You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bumping to 3.3 has (what I believe to be a potentially breaking) change:
Unencrypted User and Page access tokens, which were deprecated in 2012, will no longer be accepted by any of our APIs.
I'm really not too familiar with their graph API, but I believe this would require updating the README to notify users to use encrypted credentials (or doing the workflow for them), and, realistically, releasing a breaking change/major version bump.
@ueberauth/developers If y'all have any idea guidance on how I could test this, I'd be happy to make the changes, but I just wanted to drop-off my findings either way.
This is pretty serious but I'm rather out-of-touch with Facebook's GraphAPI at this point. I'm open to a PR @Ianleeclark that would address this, how best to test it I'm not entirely sure 🤔
Just an FYI that the v2.8 API endpoint will be EOL soon so the default
token_url
config will need to be updated.More details here: https://developers.facebook.com/docs/graph-api/changelog
The text was updated successfully, but these errors were encountered: