-
Notifications
You must be signed in to change notification settings - Fork 80
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
Unstable sign out #78
Comments
@estorski Thanks for reporting the issue! I'll investigate on the issue, meanwhile, can I know the browser and the version that you can repro the issue? Internal Ref: OKTA-364608 |
Hey @shuowu The browser is Chrome Version 87.0.4280.141 (Official Build) (64-bit) |
@estorski I am not able to reproduce the issue with our react sample app. Please feel free to reach out to our support staff at [email protected] to collect reproduction details. |
Hello, @shuowu @estorski I have the same issue. libs (5.1.1 for @okta/okta-react and 4.9.0 for @okta/okta-auth-js). |
Relates to #148 Try workaround: #148 (comment) |
Hi,
We have an issue in the up to date version of @okta libs (4.1.0 for @okta/okta-react and 4.6.1 for @okta/okta-auth-js).
We use OKTA-hosted login page.
Repro steps:
void oktaAuth.signOut();
and that's it;Actual result:
localStorage
, things likeokta-token-storage
and others) and navigate the application;OR
The two above scenarios happen unstably one or another, like 50/50.
It seems like there's some kind of a race condition, or maybe some dependency on the random order of events emitted internally by OKTA on
localStorage
update.The text was updated successfully, but these errors were encountered: