Windows Desktop: Google Sign-In Completes in Browser but Antigravity Fails to Finish Login (OAuth callback not processed + internal path error)

Google Antigravity
,
1

Description:
I am encountering a critical issue on Windows 11 where the desktop Antigravity application never completes the login process. The Google OAuth flow in the browser successfully authenticates, but the application does not finish onboarding or receive the OAuth callback. As a result, the UI remains stuck on the sign-in screen and I cannot use the IDE.

Additionally, the app logs an internal exception immediately after startup:

[BrowserOnboardingClientServer] Browser onboarding server started on http://localhost:
[uncaught exception in main]: Error: Failed to set path
at …\main.js:92:39773

This exception seems to precede and potentially block normal initialization steps, including the registration of the OAuth callback handler.

I have tried multiple troubleshooting steps — including fresh user-data directories, verifying environment variables and write permissions, testing different browsers, and reinstalling — but the behavior persists.

Steps to Reproduce:

  1. Launch the Antigravity desktop application on Windows.

  2. Click “Sign in with Google.”

  3. The browser opens and the Google OAuth login completes successfully.

  4. The browser attempts a redirect (e.g., http://localhost``:<port>/oauth-callback...).

  5. The desktop fails to receive the callback; UI remains on the sign-in screen.

  6. The terminal logs the “Failed to set path” error before any token processing.

What I’ve Tried:

  • Clean uninstall & reinstall of Antigravity + removal of AppData cache/config

  • Using multiple browser types (Chrome, Edge)

  • Creating fresh user-data dirs via --user-data-dir

  • Verifying write permissions of AppData folders

  • Running without system proxies/VPN

  • Switching default browser and registry verification of protocol handler

Technical Observations:

  • OAuth finishes with “successfully authenticated” in the browser.

  • Browser redirects to the localhost callback URL but the app never handles it.

  • The internal error in the logs is:
    Error: Failed to set path at … main.js

  • Callback returns 404 “Not found” when tested manually.

  • Related community reports suggest other Windows users are experiencing post-auth callback failures.

This bug completely prevents usage of the Windows desktop client despite successfully authorizing with Google.

1 Like