"Further action is required to use Antigravity" loop despite successful browser verification — please reset backend entitlement flag

Hi team, I’m stuck in the “Further action is required to use Antigravity. Please verify your account, then sign in again to continue” loop on the desktop IDE (v2.15.0, macOS).

Timeline of what I’ve tried:

  1. Browser OAuth completes and shows “Authentication was successful” — 3 separate times (12:08, 16:26, 16:36 CST), each time Antigravity is listed in the authorized products
  2. After each success, the IDE still returns to the Verify screen
  3. Account region: Taiwan (supported); personal Gmail; age verified
  4. Cleaned all local state (~/Library/Application Support/Antigravity, ~/.gemini), killed lingering language_server processes, re-authed fresh
  5. Verified network: clean US exit IP (risk score 0, not flagged as proxy), all Google endpoints reachable; also tested from iPhone with the same node
  6. Set up Google Prompt + passkeys for 2SV; removed phone number to change challenge types
  7. language_server.log shows repeated loadCodeAssist calls that never succeed, and “error getting token source: You are not logged into Antigravity”

Everything client-side checks out — could you please review/reset the backend entitlement flag for this account? Happy to provide the account email privately.

Hi @chenyumai,

The main issue here is the US exit node / VPN.

Taiwan is already officially supported, so routing through a US proxy is unnecessary and triggers Google’s datacenter/geo mismatch flags. That’s why browser OAuth succeeds, but the backend loadCodeAssist check gets blocked.

Here’s how to fix it:

  1. Turn off the VPN and sign in directly from your native Taiwan connection.
  2. Clear macOS Keychain by deleting local app folders misses the system keychain. Open Keychain Access, search for Antigravity, and delete any saved keys.
  3. Go to myaccount.google.com/connections, remove Google Antigravity, and do a fresh sign-in.
  4. Visit policies.google.com/terms (scroll to the bottom) to confirm your account is officially set to Taiwan.

Let me know, is the issue resolves or the issue still persists?