React-native-auth0: clearSession not work

[zhulichaoZW]

clearSession can not logout, and not enter the success callback or error callback, no console execute.

auth0.webAuth.clearSession({federated: true}).then(() => console.log('success')).catch(() => console.log('error'));

[ananova]

I've been trying to find a solution for this for a while as well.

I am presented with:

If I click cancel, I then get an error.

[cocojoe]

Ah yes I see, in this case the operation was successful. However, the browser didn't close.
Can you try adding your Callback URL to the Allowed Logout URLs section of your application in the Auth0 Dashboard

[reedyrm]

@zhulichaoZW I had a similiar problem where I was calling clearSession({}), I was able to fix the issue by adding the clientId as part of the parameters to clearSession

clearSession({clientId: "...."})

[yoo-hooo]

Hey, this seems to be a regression in v1.4.0. I had the same problem when implementing it in my application, just a blank screen with "ok" displayed on it when trying to execute clearSession() on iOS.

I tried @cocojoe 's and @reedyrm 's possible solutions, but neither of those worked in my case.

I was able to fix this issue in my application by going back to the previous version (v1.3.1).

[jhtomlee]

I have the same problem and tried all @cocojoe 's @reedyrm 's and @delanoyejonathan 's solutions but none of them work for me. I also tried logging and seems like clearSession() is not returning anything, since the second log below does not print. I'd appreciate some help!

_onLogout = () => {
    console.log("This one logs")
      auth0.webAuth
        .clearSession({})
        .then(success => {
          console.log("This one does not")
          this.setState({ accessToken: null });
        })
        .catch(error => console.log(error));
  };

Edit:
I tried @reedyrm 's solution again and it worked!

[wprk]

I had the same issue, tried combinations of all the above solutions and reverting to v1.3.1 was the only thing that worked for me. Thanks @delanoyejonathan

[alexpyoung]

It might also be worth noting that, in v1.4.0, the consent dialog appears before the web view @ananova showed. Ideally, this should not happen as the user has already consented to storing web data when authenticated and this action only removes stored data.

I was also able to resolve this issue by reverting to v1.3.1, where the alert is not presented

[winseyli]

@alexpyoung thanks for finding this. We are implementing this today and were not happy with the consent dialog. It happens on v1.4.0 but not v1.3.1
Not sure if this dialog will happen in all future releases after v1.4 ...?

[factsfinder]

Implementing both @reedyrm and @cocojoe solutions fixed the issue in my case.

[BoKKeR]

I fixed this using all the tips in this thread (even downgrade). Something to note:

Note that if the clientID parameter is included, the returnTo URL that is provided must be listed in the Application's Allowed Logout URLs in the Auth0 dashboard. However, if the clientID parameter is not included, the returnTo URL must be listed in the Allowed Logout URLs at the account level in the Auth0 dashboard.

And it only started to work after I rebuilt the app

[lbalmaceda]

The iOS redirection is fixed in the release 1.5.0. If this continue to happen, please re-open.

[drewdecarme]

I'm still getting this "error" in 2.3.0. Exact same issue as above, where there isn't a promise being returned as well as the "Sign in" dialog.