This happened when your account existed in our system but hadn't been fully set up through the normal sign-in path. The OAuth handoff would reach an intermediate state that our sign-in flow wasn't equipped to display, so the screen simply froze. The same blank-page outcome could occur if you arrived via OAuth on a path where new sign-ups aren't open.
Both failure modes now show a clear error message at the point where things go wrong. If the OAuth callback takes too long to resolve, a fallback prompt appears after a short wait so you can retry rather than wait indefinitely.
If you encountered this — a spinner that never resolved after clicking "Sign in with Google" or "Sign in with Microsoft" — try signing in again. If you continue to have trouble, contact support and we can get your account set up correctly.