BUG: Endless Login Loop / Unleash 404 Error

Google Antigravity
1

Environment:

  • OS: macOS

  • App: Google Antigravity (Public Preview)

  • Account Type: Jio-provisioned Pro Tier

Description: I am experiencing a hard authentication blocker in the Antigravity IDE. When attempting to log in using a specific Jio-provisioned free-tier account, the IDE gets stuck in an endless loop on the “Sign into Google” screen. The browser completes the OAuth handshake, but the IDE fails to authenticate the session.

This issue is strictly account-specific. I can log in perfectly fine on the exact same machine using a standard free Gmail account

Console Logs (The Root Cause): Pulling up the Developer Console during the login loop reveals that the internal Unleash feature-flag service is throwing a 404 for this specific account type, which seems to silently crash the auth flow:

Plaintext

POST https://127.0.0.1:<port>/proxy/unleash/frontend 404 (Not Found)
Unleash: Fetching feature toggles did not have an ok response
[AntigravityUnleashService] [object Object]

(I have attached a screenshot of the full console output to this post).

image
image1920×1241 335 KB

Troubleshooting Steps Already Taken (None Worked):

  1. Completely wiped local application data (rm -rf ~/Library/Application Support/Antigravity and ~/.antigravity).

  2. Wiped the extensions cache (rm -rf ~/.antigravity/extensions).

  3. Bypassed browser cache by using an Incognito window / completely fresh default browser for the OAuth redirect.

  4. Created a completely fresh macOS user profile to rule out local system conflicts.

It appears the Unleash backend is failing to return valid feature toggles for this specific tier of Jio-partnered accounts, causing the IDE to reject the login without surfacing a front-end error message.

Could the engineering team look into how these specific Jio tokens are being handled by the Unleash service?

2

On a second thought these errors also persist in free gmail account through which I am able to sign in… so errors might not be the correct debug point.