fix(auth): remove session when it has been revoked #802
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
Considering the scenario where a user is logged on both web and mobile using the Swift SDK, when the user signs out from the web using global scope, all sessions are removed from the auth service, including the session from the mobile app.
Any authenticated call made by the Swift SDK after that will throw an error and get it stuck in a state where it says it is signed in, but the session isn't accepted by the server.
What is the new behavior?
Once the SDK gets a
session_not_found
orrefresh_token_not_found
error returned by the auth service, the SDK removes the session from storage and triggers aSIGNED_OUT
event, cleaning up state.Additional context
Add any other context or screenshots.