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
Bolt.new can't find authentication flow that works. Expected behavior is that when no auth is found, the app will redirect to the login screen, otherwise it should land on a list of tasks. The loading widget appears and goes no where.
Any loading of the application should go through the auth process. The app gets stuck and the loading widget will spin indefinitely without a redirect
(Bolt.new has tried 10+ times to resolve it in different ways but cannot seem to find a solution. )
Expected behavior
Auth is checked, when no auth, user is directed to login or sign up if a new user.
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = 132.0.0.0
Major version = 132
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36
performance.memory = {
"totalJSHeapSize": 125903828,
"usedJSHeapSize": 119081724,
"jsHeapSizeLimit": 4294705152
}
Username = b33son
Chat ID = 11c2052fae86
Client version = 4b345df
Server version = 4b345df
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
Bolt.new can't find authentication flow that works. Expected behavior is that when no auth is found, the app will redirect to the login screen, otherwise it should land on a list of tasks. The loading widget appears and goes no where.
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-x3uejv3d
Validations
Steps to reproduce
(Bolt.new has tried 10+ times to resolve it in different ways but cannot seem to find a solution. )
Expected behavior
Auth is checked, when no auth, user is directed to login or sign up if a new user.
Screen Recording / Screenshot
No response
Platform
Additional context
No response
The text was updated successfully, but these errors were encountered: