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
Describe the bug
I have the autoLoginPartialRoutesGuard on the main root of the site (although callback is not guarded). I run checkAuth on init of app.component. If the user refreshes the page they are presented with a blank screen. It is because the guard is preventing the route however the checkAuth is showing the user is auth'ed.
Expected behavior
I would expect the guard to allow the page load as the user is authenticated
Is it a race condition? I've also tried removing the checkAuth in the app.component and using the withAppInitializerAuthCheck() but it didn't help. I am using localstorage
Below shows that the guard blocks the route however oninit checkAuth() shows authenticated...after the route is blocked. This ALSO has withAppInitializerAuthCheck() running
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
I have the autoLoginPartialRoutesGuard on the main root of the site (although callback is not guarded). I run checkAuth on init of app.component. If the user refreshes the page they are presented with a blank screen. It is because the guard is preventing the route however the checkAuth is showing the user is auth'ed.
Expected behavior
I would expect the guard to allow the page load as the user is authenticated
Is it a race condition? I've also tried removing the checkAuth in the app.component and using the withAppInitializerAuthCheck() but it didn't help. I am using localstorage
Below shows that the guard blocks the route however oninit checkAuth() shows authenticated...after the route is blocked. This ALSO has withAppInitializerAuthCheck() running
The text was updated successfully, but these errors were encountered: