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
I haven't tested this with more Google accounts than just, like, my own main account - which already does have an email-based account - so that could be junking it up but as I posted in Discord, that's bad enough!
Ok, I think that:
1) our email-based login works fine
2) our Google-account-based login might be broken in a way that's annoying to fix (details later) but I'm NOT sure about that
3) our Google-account-based login is DEFINITELY hard-broken if you have an email associated with said Google account already in our system
More generally we have an issue that the library we imported to do the signup hasn't been updated in 6 years and that's bad.
Firebase changed how the API worked and I can't figure out how to get
Azure to properly reverse proxy the calls. It's like some sorta CORS but
for browser cookies and anywayways it's apparently remediable but I'll
be dammned if I have the time and energy to fix it, especially since
preview is this Friday.
Anyways we're disabling everything but email and I hope that works lmao
I believe but can't really currently prove that our "Sign in with Google" uses signInWithRedirect, and I believe it's flat-out broken. See:
The result of this is that nobody can sign in with Google. Which seems bad.
Since we do not host using Firebase, we'll need to remediate using one of the following: https://firebase.google.com/docs/auth/web/redirect-best-practices#web_1 or we need to disable to "Sign in with Google" sign in method.
See also #844
The text was updated successfully, but these errors were encountered: