I am completely unable to log in to the Antigravity desktop app. The UI freezes indefinitely at the “Sign in with Google” waiting screen. While the browser authentication completes successfully, the app fails to process the callback and returns to a dead state.
Environment & Critical Edge Case:
OS: Windows
Account Status: Upgraded to Gemini AI Pro today.
Crucial Context: This specific account was long-dormant (inactive for a long period) prior to today’s upgrade.
Troubleshooting done: I have tested logging in with a different, standard free Gmail account, and it worked perfectly. This proves the issue is specifically tied to the payload of the upgraded dormant account.
It is highly likely that this combination (legacy account structure + new AI Pro subscription payload) introduces huge integers (like 64-bit legacy Gaia IDs, quotas, or timestamps) into the auth callback payload.
Steps to Reproduce:
Launch Antigravity.
Click the “Sign in with Google” button.
Complete the OAuth flow in the browser.
Return to the app → The screen is stuck and does not proceed.
Technical Details & Root Cause:
By running the application from the CLI using --open-url "antigravity://auth", I caught the main process crashing due to an unhandled BigInt serialization error during the authentication callback phase.
It appears that JSON.stringify in main.js cannot natively handle the BigInt values present in the payload of this specific account state.
Error Logs:
C:\Users\[My Username]\AppData\Local\Programs\Antigravity\Antigravity.exe --open-url "antigravity://auth"
[main 2026-03-13T02:50:01.040Z] [uncaught exception in main]: TypeError: Do not know how to serialize a BigInt
[main 2026-03-13T02:50:01.043Z] TypeError: Do not know how to serialize a BigInt
at JSON.stringify (<anonymous>)
at vD (file:///C:/Users/[My Username]/AppData/Local/Programs/Antigravity/resources/app/out/main.js:31:11765)
at nve.o (file:///C:/Users/[My Username]/AppData/Local/Programs/Antigravity/resources/app/out/main.js:31:14636)
at nve.m (file:///C:/Users/[My Username]/AppData/Local/Programs/Antigravity/resources/app/out/main.js:31:14511)
...
I managed to resolve the login issue by modifying a core main.js file in Antigravity.
Steps to fix:
Navigate to the location indicated in your logs: …/main.js:31:11765 (Line 31, position 11765).
Locate the following code: JSON.stringify(t)
Replace it with this snippet to handle BigInt serialization: JSON.stringify(t,(_k,v) => typeof v === "bigint" ? v.toString() : v)
This change should allow the login process to complete successfully.
This is a temporary workaround. If Antigraviti is updated or reinstalled, main.js will be overwritten and you will need to apply this change again. I hope Google addresses this issue soon so this manual fix isn’t necessary.
@pedrazadixon Thank you so much for the brilliant workaround! I applied the fix to main.js, and it worked perfectly.
More importantly, your fix revealed the true root cause of the crash, which should be a huge clue for the Google dev team:
It turns out my Google account was temporarily locked for security reasons (likely because it was a long-dormant account that I had just upgraded to AI Pro).
Before applying your fix, Google’s auth server was trying to serve a security challenge (QR code or SMS verification). However, the security payload contained the BigInt. Because main.js crashed during serialization, the app simply froze and never displayed the verification screen.
Once I applied your patch, the app successfully handled the BigInt and finally displayed the challenge. Interestingly, when I tried SMS verification, I got a “This phone number has been used too many times” error, so I used the QR code to verify my identity instead. After completing the verification, the lock was lifted and I successfully logged into Antigravity!
Thanks again for your help. I hope the dev team sees this so they can handle security payloads properly in the next update!