Skip to content
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

Closed
sabafromwandio opened this issue Sep 16, 2019 · 9 comments
Closed

LoginManager.logOut() not working #580

sabafromwandio opened this issue Sep 16, 2019 · 9 comments
Labels

Comments

@sabafromwandio
Copy link

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

@Rasalexman
Copy link

I heve the same issue

@KylinChang
Copy link
Contributor

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.

@thanakitskp
Copy link

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

@KylinChang
Copy link
Contributor

KylinChang commented Sep 30, 2019

Hi @thanakitskp , do you use the latest version(v5.5.1) of SDK?

@babkouew
Copy link

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.

@ranjandas503
Copy link

ranjandas503 commented Dec 6, 2019

I am also getting the same issue, have anyone got any solution for that.
I have used version 5.5.1 and 5.12.0 and getting the same issue.

I switched to version 5.0.3 until it is fixed

@stale
Copy link

stale bot commented Mar 5, 2020

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.

@stale stale bot added the Stale label Mar 5, 2020
@stale
Copy link

stale bot commented Mar 12, 2020

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.

@stale stale bot closed this as completed Mar 12, 2020
@shahzadafridi
Copy link

shahzadafridi commented Sep 12, 2020

If someone is still facing issue then there is a solution which worked for me.

   if (AccessToken.getCurrentAccessToken() != null) {
            GraphRequest(
                AccessToken.getCurrentAccessToken(), "/me/permissions/", null, HttpMethod.DELETE,
                GraphRequest.Callback {
                    AccessToken.setCurrentAccessToken(null)
                    LoginManager.getInstance().logOut()
                }
            ).executeAsync()
        }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants