-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sign up error : Unable to process request due to missing initial state #1109
Comments
It seems like this issue.#233. |
btw, How to fix the confusing login flow issue is here: How to fix the proxy issue is here: |
@robdew Thanks for the report! Two questions:
Also, you should only have to go through this login flow once, so if you test with a different browser and it works, you shouldn't have to use that browser for login again in the future. |
Same error message today. Firefox is configured to allow, but ask me, to use persistent storage. Here are the additional tests I added to my firefox login: I signed out of github, because this allowed the I went to I signed in to github successfully, then the same error message appeared. I switched to Chrome and it works OK, so I think it is safe to write this off as a strange interaction with Firefox multiaccount containers and Firebase (since other Github auth apps work fine). I am used to the occasional quirk like this, but it rarely can't be resolved by manually changing the login workflow like I tried above. |
Should be fixed! |
Discord username (optional)
No response
Describe the bug
To Reproduce
Open warp app
click sign up
go to browser window (https://app.warp.dev/signup/remote?scheme=warp&public_beta=true)
click Sign up with Github
brief browser popup window appears, then disappears, then this message is displayed:
Unable to process request due to missing initial state. This may happen if browser sessionStorage is inaccessible or accidentally cleared.
Url (somewhat redacted) is: https://astral-field-294621.firebaseapp.com/__/auth/handler?.......
I am unsure what part of the URL is sensitive information.
Expected behaviour
Screenshots
No response
Operating System
MacOS
OS Version
11.6.5
Additional context
The text was updated successfully, but these errors were encountered: