You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
so far, seeing a similar problem, but this appears to be caused by the server response and/or environment, not the library. I checked if a console fetch will have similar issues, and the headers are not readable. Therefore this library is also not seeing the headers when needed. Given a lack of any other information I have to go on this.
I know it is a year late response, but hopefully helpful to anyone coming across this. Related to the CORS functionality, auth headers can't be read by xhr by standard configs.
I'm sure there's some other considerations I need to make, but you'd need to expose them in your CORS config, so an example from rails:
SignInUser is neither setting headers nor persisting the headers in the local storage even after successful login signInRequestSucceeded.
The text was updated successfully, but these errors were encountered: