Persistent Google sign-in failure after update — multiple fixes attempted, still blocked

Google Antigravity
1

Hi Antigravity team / community,

I’ve been unable to sign in to Antigravity since updating the app. I’ve gone through extensive troubleshooting and I’m still blocked. Posting full details in case this helps diagnose it or helps others hitting the same thing.

Environment

  • OS: Windows
  • Browser: Chrome (default)
  • Issue started: right after updating Antigravity

Timeline of symptoms and what I’ve tried

  1. Initial symptom: Clicking “Sign in with Google” left the app frozen indefinitely on “Awaiting Authentication…” — no browser window opened, no error, just stuck.

  2. Fix attempted — cache/onboarding reset: Ran “Antigravity: Reset Onboarding” from the command palette, then backed up (renamed, not deleted) these folders:

    • %APPDATA%\Antigravity
    • %USERPROFILE%\.gemini\antigravity
    • %USERPROFILE%\.gemini\antigravity-ide
    • %USERPROFILE%\.gemini\antigravity-browser-profile (found this one wasn’t in the standard list, but it appears to hold the embedded browser/auth session)

    Result: This got me past the frozen screen. Clicking sign-in now actually triggered the Google OAuth flow. However, after completing sign-in, I got a new error:

    “There was an unexpected issue setting up your account.”
    Subtext: “context deadline exceeded”

  3. Fix attempted — revoke and reconnect account access: Went to myaccount.google.com/connections, found Antigravity, and used “Delete all” to fully remove the account link (confirmed this doesn’t delete any Antigravity data, just the connection). Reopened Antigravity and tried signing in again.

    Result: Back to a browser tab opening on sign-in, but this time the tab itself displayed an error (I don’t have the exact error text saved yet — can grab it on request).

Where I’m at now
I’m about to try a full uninstall/reinstall (removing the app plus %LOCALAPPDATA%\Programs\Antigravity, antigravity-updater, and the temp installer folder) but wanted to post here first in case this is a known/server-side issue, since “context deadline exceeded” suggests a backend timeout rather than something purely local.

Has anyone else hit this specific sequence (frozen auth → cache reset → context deadline exceeded → account relink → browser error)? Any insight from the team on whether this is a known regression would be appreciated.

Happy to provide logs, the exact browser error text, or anything else that helps debug this.

Thanks!

1 Like