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
Run the app, open the Login Manager Example and tap 'Invoke login method' and complete login
Take note of the authentication token on the Login Details page that shows
Go back
Tap 'Invoke login method' again and complete login
Observe that the authentication token is the exact same token on the Login Details Page
Undo changes from step 2
Repeat step 3-7
Observe the authentication token changes with each login as expected
Code samples & details
This can be worked around by explicitly passing the trackingPreference but is quite confusing with the latest SDK version automatically opting into limited login without passing explicitly in the config. It is a risk if anything goes wrong with converting the initial login to a session users can end up locked out from Facebook login.
The text was updated successfully, but these errors were encountered:
I understand that but it isn't the issue at hand, the authentication token returned from the SDK does not refresh unless you explicitly pass the .limited param which feels like a bug.
Checklist before submitting a bug report
Xcode version
15.1
Facebook iOS SDK version
17.0.0
Dependency Manager
CocoaPods
SDK Framework
Login
Goals
To consistently get a valid jwt token when invoking the login method in the Facebook sdk
Expected results
Anytime I invoke the Login methods on the sdk a new authentication token should be returned that can be verified and converted into a user session.
Actual results
Repeatedly receive the same authentication token even after expiry on subsequent Login invocations.
Steps to reproduce
You can reproduce this bug in the sample login app in this repo with some small changes:
Code samples & details
This can be worked around by explicitly passing the trackingPreference but is quite confusing with the latest SDK version automatically opting into limited login without passing explicitly in the config. It is a risk if anything goes wrong with converting the initial login to a session users can end up locked out from Facebook login.
The text was updated successfully, but these errors were encountered: