Issue Description: I am completely locked out of the Antigravity IDE on my primary developer account. The authentication either fails silently or loops indefinitely. However, a secondary Google account logs into the IDE perfectly on this exact same machine and network, isolating the issue entirely to this specific account’s backend state.
Troubleshooting Steps Already Taken:
Isolated the Environment: Logged in successfully with an alternate account, ruling out local OS conflicts, firewall issues, or WSA/WSL link hijacking.
Verified Account Type: Confirmed the problem account is a standard @gmail.com address, not a Workspace/custom domain.
Regional IP Alignment: Locked in a definitive account region via a new Google Payments profile. Because I am based in Brazil but manage a US-based Wyoming LLC and US Play Store developer accounts, I ensured my active IP strictly matched the account’s registered region during the login attempt to avoid cross-border security flags.
Clean OAuth State: Cleared all cookies for accounts.google.com and executed the login via a fresh Incognito window.
Nuked Local App Data: Completely deleted all local Antigravity application data and caches before retrying.
Expected Behavior: The OAuth redirect (antigravity://auth) successfully passes the token to the IDE, provisioning the account for use.
Actual Behavior: Browser authentication succeeds, but the IDE ignores the token or silently fails to provision the account.
Request: Given that all local and regional variables have been cleared, this account appears to have a corrupted OAuth token cache or is stuck in a provisioning loop on the backend. Could an engineer please review the server-side state for the account posting this?
Tagging @pradeepkuppala - could you or someone on the Antigravity team please check the backend provisioning state for this account? I am completely locked out despite all local/regional troubleshooting.
Thank you for bringing this to our attention. We have escalated the issue to our internal teams for a thorough investigation.
To ensure our engineering team can investigate and resolve these issues effectively, we highly recommend filing bug reports directly through the Antigravity in-app feedback tool. You can do this by navigating to the top-right corner of the interface, clicking the Feedback icon, and selecting Report Issue.
Hello @Abhijit_Pramanik Thank you for you support. I will follow the procedure you advised moving forward, but this time I followed the procedure that was recommended to me by Gemini itself.
Hi @Abhijit_Pramanik - Kinda difficult to do this when the login fails. It does work with an account that is not subscribed to any tiers, fails with an account on the Ultra plan. Feel if I submit via the free account, it is not going to matter and might be a distraction from the main issue at large - its either an account problem (gemini works, cli and agy fail).
The account that fails has this in the logs:
2026-03-27 21:35:18.289 [error] TypeError: Do not know how to serialize a BigInt
at JSON.stringify ()
at jW (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:31:11784)
at YHe.o (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:31:14666)
at YHe.m (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:31:14539)
at iee.value (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:32:265)
at un.C (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:30:2354)
at un.D (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:30:2424)
at un.fire (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:30:2642)
at iee.value (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:28:6950)
at un.C (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:30:2354)
at un.fire (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:30:2573)
at G_e.U (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:4540:58637)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:4540:55041
2026-03-27 21:35:18.290 [error] [uncaught exception in main]: TypeError: Do not know how to serialize a BigInt
2026-03-27 21:35:18.290 [error] TypeError: Do not know how to serialize a BigInt
at JSON.stringify ()
at jW (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:31:11784)
at YHe.o (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:31:14666)
at YHe.m (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:31:14539)
at iee.value (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:32:265)
at un.C (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:30:2354)
at un.D (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:30:2424)
at un.fire (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:30:2642)
at iee.value (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:28:6950)
at un.C (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:30:2354)
at un.fire (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:30:2573)
at G_e.U (file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:4540:58637)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async file:///Applications/Antigravity.app/Contents/Resources/app/out/main.js:4540:55041
2026-03-27 21:35:32.644 [info] update#setState checking for updates
2026-03-27 21:35:33.134 [info] update#setState idle