I can see a tracking id but I don’t know how to debug using that. When the user comes back to sing in, then it works fine. I don’t know what wrong here. I’ve integrated auth0 with AWS Cognito and I’m using sign in with LinkedIn
Based on your screenshots, I was able to correspond the “Failed to load previous state” error to an event found in your tenant logs. It seems that what happened was that the user attempted to access the login page directly instead of starting the login flow from the beginning (/authorize).
And by not doing so, this caused the state error.
The error description in your logs also states the following:
A user has attempted to access a login page directly. This is not supported unless a “Application Login URI” is set for your application, or a “Tenant Login URI” is set for your tenant. For more information, see: Configure Default Login Routes
Seeing that, you should be able to fix this error by configuring your default login routes on either the application or tenant level.
We only have a mobile (React native based) client for this app and I don’t think we can create and https based login page using the react native app. Any thoughts on this?
Also, I’m not sure how the user attempts to access the login page directly instead of starting from the beginning. We’ve set this configuration inside our react native app: