-
Notifications
You must be signed in to change notification settings - Fork 232
Unhandled Rejection (AuthSdkError) #885
Comments
@Dark-Games I failed to reproduce your issue with cache and cookies cleared. I would be happy to investigate more if you can share detailed reproduction steps. |
@shuowu |
@Dark-Games I don't think it's caused by your configuration, probably it comes from your code, which triggered multiple pkce login flow concurrently. |
@shuowu I will try to send to you the code that i'm using because i searching for what was the cause but didn't found nothing wrong. If you find something wrong with the code i appreciate! App.js
routes.js
auth_okta.js
app_bar.js
|
Maybe i discovered the error, when i add a button to the authService.login() the website start working again or with a wait function. But exist someway to do that without use a button or a wait function? |
@Dark-Games Exactly. Looks like you introduced I would suggest to only keep one approach to handle app authState, the way from If you are using the |
@Dark-Games Could you please explain what was the issue exactly, because I'm also getting the same issue when I clear my cache. Sometimes it works. I'm using both custom login and okta-hosted-log(tile-login). |
I'm submitting this issue for the package(s):
I'm submitting a:
Current behavior
If i clear the cache and cookies before Login i have this error:
Unhandled Rejection (AuthSdkError): The app should not attempt to call getToken on callback. Authorize flow is already in process. Use parseFromUrl() to receive tokens.
Expected behavior
Login with success
Minimal reproduction of the problem with instructions
Before try to login i clear the cache and cookies and have this issue,
If i try to login again without clear the cache, dont show this error
Extra information about the use case/user story you are trying to implement
I just want to know if someone have this same issue or what can be the cause
I tried to search what part of the code have this issue and i think it is the LoginCallback, but i dont know how change that component
Environment
The text was updated successfully, but these errors were encountered: