Antigravity login bug: OAuth succeeds, but app never completes sign-in for one specific personal Gmail account

Hello Antigravity team,

I’m experiencing a persistent login failure with Google Antigravity Desktop.

Title: OAuth succeeds but the app never completes sign-in.

Environment

  • OS: Windows 11
  • Account type: Personal Gmail
  • Subscription: Google One AI Pro (2TB)
  • App: Latest Antigravity Desktop
  • Region: Korea

Problem description

When I try to sign in with my Google account:

  1. I click “Sign in with Google”
  2. Browser OAuth authentication completes successfully
  3. The browser shows that authentication succeeded
  4. When returning to the Antigravity app, the onboarding never completes
  5. The app remains stuck and I cannot proceed

Important detail

  • Other Google accounts can log in successfully on the same PC and network.
  • Only my primary Gmail account fails to complete the sign-in process.

Troubleshooting already attempted

  • Reinstalled Antigravity multiple times
  • Deleted local data (%AppData% / Antigravity folders)
  • Removed Antigravity from Google third-party access
  • Cleared browser cookies and OAuth sessions
  • Tried different networks
  • Disabled VPN
  • Logged out/in of Google account
  • Restarted PC

None of these resolved the issue.

Because OAuth authentication succeeds but onboarding fails only for this specific account, it appears the Antigravity account setup state may be stuck server-side.

Could someone from the Antigravity team check the backend account provisioning state and reset the onboarding status for this account?

Thank you.

I have the same exact problem

Same issue here. I need to login urgently but its failing. Its ridiculous.

Hello,

Thank you for sharing your concern with us. To help resolve the issue with your login, please review the following checklist:

  • Age Verification: You may need to verify your age to unlock increased quotas. You can complete this process at the following link: https://myaccount.google.com/age-verification.
  • Regional Availability: Please note that upgraded quotas through Google One are not currently available in all locations. We recommend referring to the full list of supported regions here to confirm availability in your area.
  • Account Status: Please ensure you are signed in with the correct Google Account associated with your Pro subscription. You can verify this by opening the Settings menu in Antigravity and clicking on Account in the left-hand sidebar. If the wrong account is listed, simply click Sign out and log back in with the correct credentials.

Thank you for the checklist.

I completed age verification, but the issue still persists.

Current status:

  • Age verification is completed.
  • I am using the correct personal Gmail account with Google AI Pro.
  • The same issue occurs on multiple PCs/laptops.
  • Other Google accounts can log in successfully, but only my primary Google AI Pro account fails after OAuth succeeds.

Since the issue persists across multiple devices and only affects this specific account, it may be related to an account-specific onboarding or provisioning state.

Could you please check if there might be any issue with the backend setup for this account?

If needed, I can share my app version and OS version.

Were you able to resolve this issue?

Same here, try everything from re-install, clean cache, change browser, disable VPN and use VPN to change location to other country, check all the requirement like Age verification, location,… and also change PC/Laptop but still not worked.

This only affect to my main gmail account, email to Google Antigravity Support team for a week and still no reply from them.

Has anyone resolve this issue?

I found the solution: Fix for Antigravity App Login Crash (TypeError: Do not know how to serialize a BigInt) · GitHub

And it’s worked for me.

Thanks for sharing the solution.

I checked this, but my case does not seem related to the BigInt error.
There is no such error in the logs, and the issue still persists after OAuth succeeds.

It seems like a different issue, possibly account-specific.

Did you try to debug like the link said ? I thought it was account-specific but it actually the Antigravity App Library error. I meet exactly the same error situation like you.

1 Like

Thanks so much — I had been struggling with this for 3 weeks, and your comment finally helped me solve it. I really appreciate it. I can’t tell you how relieved I am.

I was finally able to solve this, so leaving an update here in case it helps someone else.

At first, I thought this was an account-specific issue because only my main Google account failed, while other Google accounts worked fine on the same PC and network.

While debugging on one Windows device, I found this Antigravity app error in the logs:

TypeError: Do not know how to serialize a BigInt

Because of that, I initially thought the app-side BigInt error was the main cause. I tested the workaround by editing main.js and adding:

BigInt.prototype.toJSON = function() { return this.toString(); };

That helped the login flow move forward to the next step, where Antigravity asked me to verify my Google account. I completed the SMS verification flow, clicked Sign in again, and then the main account was able to log in.

What makes me think the bigger root cause was the Google account verification state is that, after completing that verification, my main account also started working on other devices without applying the BigInt workaround there.

So in my case, it seems this involved both:

  • an Antigravity app-side BigInt error seen during debugging on one device
  • and a Google account verification issue that was likely the bigger blocker overall

What I did:

  1. Ran Antigravity in debug mode from PowerShell
  2. Tried signing in again and checked the logs
  3. Found the BigInt serialization error
  4. Tested the main.js workaround on one device
  5. Completed Google SMS verification
  6. Clicked Sign in again and retried login
  7. Confirmed the account could log in successfully, including on other devices

I had been stuck on this for 3 weeks, so I really hope this helps someone else.