New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LoginManager.logOut() not working #580
Comments
I heve the same issue |
Hi @sabafromwandio , @Rasalexman , which version of SDK are you using? I cannot reproduce the issue, it would be better if you can share example code. |
I use default login manager like LoginManager.getInstance(), then login and logout , but when i check token after logout like this AccessToken.getCurrentAccessToken() it still exists |
Hi @thanakitskp , do you use the latest version(v5.5.1) of SDK? |
I have the same issue both on Android and iOS I use the latest sdK 5.8.0 in iOS and 5.9.0 in Android. LoginManager.getInstance() does not work. This issue has been lingering for a time now and the ticket posted in facebook-iOS-sdk github has even been archived without any hints on how to solve the problem. They however said that this was due to cookies in browsers that save token authentication data that gets automatically reused each time the user wants to login with facebook. |
I am also getting the same issue, have anyone got any solution for that. I switched to version 5.0.3 until it is fixed |
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. Thank you for your contributions. |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information. |
If someone is still facing issue then there is a solution which worked for me.
|
I use default login manager like
LoginManager.getInstance()
, then login and logout , but when i check token after logout like thisAccessToken.getCurrentAccessToken()
it still existsThe text was updated successfully, but these errors were encountered: