Problem: I am encountering a persistent login loop with Google Antigravity that only affects one specific account. When I select “Sign in with Google,” the browser opens and confirms a successful authentication with the standard redirect message. However, the Antigravity app does not respond; it remains stuck on the initial “Sign in with Google” screen without progressing to the IDE or showing any error messages.
Key Details:
Account Type: Personal Gmail account with an active Google AI Pro subscription.
Location: I am based in the United States. My IP address, region settings, and phone number are all U.S.-based and consistent.
Scope: This is an account-level issue. I have tested other Google accounts on the same machines, and they log in to Antigravity perfectly.
Troubleshooting Performed:
Tested across multiple devices (two different computers).
Swapped default browsers between Chrome and Edge (same result on both).
Confirmed the account is in good standing (not suspended, 18+ verified via credit card).
Expected Behavior: Following the browser’s OAuth success, Antigravity should automatically advance to the “Setting up your account” screen and launch the IDE.
Actual Behavior: The app remains unresponsive on the login prompt, providing no feedback or error codes.
Given that this issue persists across different hardware and browsers but is unique to this one account, it appears to be a backend synchronization issue rather than a client-side bug. I’ve noticed similar reports from other Pro subscribers—is there an internal investigation currently underway for this?
Thank you for bringing the issue to our attention. Our engineering team is currently investigating the matter, and we appreciate your patience as we work toward a resolution.
oh it sounds exactly like the thing i’ve been pushing a workaround on for the past weeks.
its exactly the same symptoms as the broken auth chain that leads to the looping 7day stuck situation. the short version is - you’ve got 2 google accounts in your browser i have been pushing this solution since the 16th, did a pretty in depth post and continue providing updates and support on it. i also just put a little flowchart together which might help understanding it. (i know i get like dyslexic codeblindness from too many words on screen sometimes so the graphic might help)
i’ve been chasing down the edge cases too where its similar enough but also presents as different symptoms slightly or seems to have similar triggers! so even if its not the same same issues and the solution doesn’t resolve it i’m glad to help troubleshoot.
I think I encountered the exact same issue with my AI Pro account. I initially suspected a backend synchronization error, but after running the app with the --verbose flag, I found a client-side crash in the main process.
In my case, the logs showed this specific error immediately after the browser redirect:
[ERROR] [main] [uncaught exception]: TypeError: Do not know how to serialize a BigInt
at JSON.stringify ()
at vD (file:///C:/Users/…/main.js:31:11765)
It seems that Pro accounts return a payload with BigInt values (likely Gaia IDs or quotas) that the native JSON.stringify in the app’s main.js cannot handle. This causes the app to hang indefinitely on the login screen.
I found another thread discussing this exact bug here:
What I tried on my end (Temporary Workaround):
I manually patched the main.js file by finding the code at line 31:11765 and replacing:
JSON.stringify(t)
with:
JSON.stringify(t,(_k,v) => typeof v === “bigint” ? v.toString() : v)
This allows the app to serialize the BigInt as a string, which fixed the crash and let me log in successfully. I hope this helps you get back into the app!
i have been pushing this solution since the 16th, did a pretty in depth post and continue providing updates and support on it. i also just put a little flowchart together which might help understanding it. (i know i get like dyslexic codeblindness from too many words on screen sometimes so the graphic might help)
