Login Error - "Unexpected issue setting up your account" - Pro subscriber, account blocked

Google Antigravity
1

Hi Antigravity Team,

I’m a Google AI Pro subscriber and I’m unable to log into Antigravity IDE. Every time I try to sign in with my personal Gmail account (the same one linked to my Pro subscription), I get the error:

“There was an unexpected issue setting up your account.”

To clarify — this is happening on BOTH my paid Pro account AND a separate free/personal account on the same device. So this doesn’t seem to be a Pro-quota-recognition issue, it seems device or IP-level.

What I’ve already tried:

  • Fully closed the app and cleared local cache (AppData/LocalAppData folders)
  • Completely uninstalled and reinstalled the IDE
  • Tried on a fresh install with the migration dialog skipped
  • The error persists exactly the same every time

Details:

  • Account: malikm********@gmail.com
  • OS: Windows
  • I have an active Google AI Pro subscription on this same account

Could someone please check the backend status for this account and let me know why it’s stuck? This is affecting my ability to use a subscription I’m paying for.

Thank you.

issue
issue846×740 12.4 KB

Update: I was able to log in successfully using a mobile hotspot (different IP/network), but my home WiFi network still fails with the same error. This confirms it’s an IP-level block, not an account issue.

2

Hi @Malik_Manan,

Yes, your account and Pro subscription are fine as this is strictly a network level block on your home Wi-Fi. The IDE’s backend process is failing an initial connection to endpoint before it even checks your account tier (usually caused by a shared CGNAT IP rate-limiting, flaky ISP IPv6 routing or router security filters). So the quick way around this:

  • Use the hotspot to sign in, then just switch back to Wi-Fi without logging out. The IDE stores your credentials locally, so you don’t need to repeat the setup on Wi-Fi.

  • Turn it off for ~5 minutes. If your ISP uses dynamic IPs, you’ll get a new public IP, which usually clears the block.

3

Just tried using a mobile hotspot and it fixed the issue completely! Thanks devs! :raising_hands: