Open curiosDevInSearch opened 1 year ago
I got the same error after sign in, is there a fix?
I see that there are similar issues in the past but these have been marked as fixed. I'm also experiencing this issue using version 3.2.2. Our IdP is Azure.
Any update? @Ploppz did you solve the issue?
Well I started using oidc-client-ts
but ... I'm still experiencing a "Error: No state in response" error, so maybe I'm just doing something wrong. In my case, the error doesn't seem to affect the application though. So I did not yet look further into this issue.
Your error may mean the response code doesn't contain state= query param.
According to the source code there should be the SignInError handler. But it's absent when you install the npm package.
Hey! We forgot to publish the SignInError handler, but that is done today! Hope that helps :)
@simenandre Thank you very much!
Uncaught (in promise) Error: No matching state found in storage at OidcClient.readSigninResponseState (oidc-client-ts.js:1785:1) at async UserManager.signinCallback
After I signed in and redirected back to my app I am getting that console error, need help to fix it