I’ve been trying to upgrade to the auth0-spa-js package using the redirect option from our current implementation using Lock with a pop up.
Consistency, my users and my self will be redirect to https://.auth0.com/u/login?state= and it will be completely blank on screen. If I click on another tab and the come back, the page will render. It will not render without leaving and returning to the page.
Browser: Chrome
SDK: auth0-spa-js
Implementation: Based on example with React (Auth0Provider)
@HLR sounds somewhat similar, but for me, I don’t even get the blank header bar, the screen is completely blank.
I’ve seen some talk in the github issue’s page about the possibility of getTokenSilently being called multiple times could cause this, but I haven’t had a chance to investigate that.
We’re having the same issue of getting stuck to on a blank page on our auth0 domain when logging in. The only additional (although probably not helpful) information I can add is that opening the browser dev tools also seem to cause the page to render correctly…
I do, but I can’t recall what it says of the top of my head, and I only get this problem sporadically and I am unable to reproduce it at will, i.e. the worst kind of problem
I’ve got the same issue, but it is not systematic.
I’m using the New Universal Login with auth0-spa-js SDK (but I think that’s not the point of the issue).
Sometimes after users log out, there is a blank page and resizing window is sufficient to bring up the login form again. It is not very comfortable for our users.
In a desktop, the media query for max-width 480px is executed, despite my zoom level being 100%. Whenever this happens we get the blank screen. On resizing the browser, this media query breakpoint is gone and the login screen is loaded. Any solution for this from the Auth0 team?
I’ve been seeing the same thing for the last month or so - when the SPA redirects to auth0, I get a blank screen about 50% of the time. Resizing the window makes the login form come up. 6 weeks and no response from the auth0 team on a deployment-blocking issue that is affecting multiple people is very disappointing.