400 on /authorize should result in error being set and/or loading being false

Describe the problem you’d like to have solved

In the screenshot below I have loaded our landing page, auth0 is silently trying to hit <auth0_tenant>/authorize and is getting a 400 back. isAuthenticated is false, isLoading is true, error is undefined, so I should just sit and wait for auth0 to do something…

Once the internal auth0 timeout eventually triggers (60s? 120s? I forget), isLoading is set to false / and error is set to Timeout.

I can then happily show my user a login page, but the user has probably gotten bored and closed the tab by that point.

Describe the ideal solution

User should not be sat at our loading screen waiting for auth0’s timeout to trigger

Alternatives and current work-arounds

Don’t show user a loading page whilst auth0 is loading…

Screenshot from Network tab

[tfmark]

Gonna close this out, last few days looks like it’s behaving as it should. Cheers!

[Alvaro948]

Hi @adamjmcgrath ,

Thanks for your anwser, had the same problem and setting useRefreshTokensFallback: false fixed the issue.

In my particular case, this was a capacitor / angular application with refresh tokens enabled.

https://community.auth0.com/t/auth0-app-id-doesnt-link-with-the-android-application/67288/4

The problem here is that the auth0 logs is telling to add “<app_id>://<domain>/capacitor/<app_id>/callback” as an Allowed origin, which leads to a much dificult error.