# Sign not working on iOS (React-native)

**URL:** <https://devforum.okta.com/t/sign-not-working-on-ios-react-native/20197>\
**Category:** Questions\
**Tags:** react-native, ios\
**Created:** [April 11, 2022, 1:51pm UTC](https://devforum.okta.com/t/sign-not-working-on-ios-react-native/20197 "2022-04-11T13:51:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![v10](https://avatars.discourse-cdn.com/v4/letter/v/da6949/32.png) [@v10](https://devforum.okta.com/u/v10)\
**Post date:** [April 11, 2022, 1:51pm UTC](https://devforum.okta.com/t/sign-not-working-on-ios-react-native/20197/1 "2022-04-11T13:51:34Z")

</div>

In iOS, when using either the browser sign-in or the custom sign-in implementations, signout(), revokeAccessToken(), revokeIdToken(), clearTokens() do not actually sign the user out. If using the browser sign-in, after signing out and then trying to re-sign in the user is able to enter the app without re-entering their user/pass. The browser sign-in page pops up and then instantly disappears and we are signed in to the app.

When I try using the custom sign-in, if “User A” signs out and then “User B” tries to sign in with different valid credentials, it returns a -600 error -“Authorization Error: Unexpected response format while retrieving authorization code.” . If I go into Okta console, find “User A” and then clear all session data/tokens, the custom sign-in will now work for “User B”. Anyone else encountered these issues?

Android works correctly.

---

<div class="post-metadata">

**Author:** ![andrea](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/andrea/32/2172_2.png) [@andrea](https://devforum.okta.com/u/andrea)\
**Post date:** [February 12, 2024, 6:27pm UTC](https://devforum.okta.com/t/sign-not-working-on-ios-react-native/20197/2 "2024-02-12T18:27:38Z")

</div>