Antigravity 2.5.5 authentication fails automatically, but manual “Try Another Email” login succeeds

Google Antigravity
1

I’m experiencing a persistent authentication problem with Antigravity IDE 2.5.5 on Windows 11.

The unusual part is that Google authentication itself succeeds. The failure occurs afterward when Antigravity tries to complete the authentication/service initialization.

Reproduction

My normal sequence is:

Launch Antigravity IDE.
Antigravity automatically attempts authentication.
Authentication fails.
I click “To Login Click Here.”
A separate account login page opens.
I click Login.
I select my Google account.
Google authentication succeeds.
The Try Another Email page reports authentication successful.
I click Next.
Antigravity becomes logged in.
The account login page also shows that I am logged into the account.

So manual authentication works, but the initial automatic authentication does not.

Network investigation

I tested the Google endpoints independently from PowerShell.

For example:

cloudcode-pa.googleapis.com

is reachable over both IPv4 and IPv6.

A direct HTTPS request to:

https://cloudcode-pa.googleapis.com/

returns:

HTTP 404 Not Found

which confirms that the server is reachable.

I also tested:

/v1internal:loadCodeAssist

with a POST request. Without credentials it returns:

HTTP 401
UNAUTHENTICATED
CREDENTIALS_MISSING

This is expected, but importantly it demonstrates that the request is actually reaching Google’s Cloud Code service.

IPv6 connectivity is also successful.

Antigravity logs

The Antigravity logs show the following errors.

auth.log:

[Auth] Error confirming user for service:
request to https://cloudcode-pa.googleapis.com/v1internal:loadCodeAssist
failed, reason: socket hang up

Later:

[Auth] Error refreshing user status:
request to https://daily-cloudcode-pa.googleapis.com/v1internal:fetchAvailableModels
failed, reason: socket hang up

And after manually logging in:

[Auth] Error confirming user for service:
request to https://daily-cloudcode-pa.googleapis.com/v1internal:fetchUserInfo
failed, reason: socket hang up

cloudcode.log also repeatedly reports:

Client network socket disconnected before secure TLS connection was established

and:

socket hang up

There is also an OAuth profile request failure:

request to https://www.googleapis.com/oauth2/v2/userinfo
failed, reason: Client network socket disconnected before secure TLS connection was established
Additional testing

I checked Windows proxy settings:

WinHTTP proxy settings:
Direct access (no proxy server)

There are no proxy environment variables configured.

I also checked Windows Firewall rules. Nothing specifically blocks Antigravity or Google outbound traffic.

I tested the Google endpoints with both IPv4 and IPv6.

Interestingly, IPv4 connectivity to some Google addresses is inconsistent, while IPv6 works reliably. However, Antigravity’s own Node processes are being started with this resolver rule:

--host-resolver-rules=“MAP daily-cloudcode-pa.googleapis.com [2001:4860:4841:400::]”

One of the Antigravity Node services also has:

--dns-result-order=ipv4first

Despite this, the authentication requests still fail with socket/TLS errors.

Another interesting finding

The Antigravity Node processes are all running from:

C:\Users\Admin\AppData\Local\Programs\Antigravity IDE\Antigravity IDE.exe

The installed version is:

Antigravity IDE 2.5.5

The executable identifies itself as:

Company: Google LLC
Product: Antigravity IDE
Version: 2.5.5
Current workaround

The workaround is:

Try Another Email → Google account → successful authentication → Continue/Next

This eventually gets me into Antigravity and I can use the IDE.

However, I have to go through this manual authentication process because the normal automatic authentication fails.

Feedback submission issue

I also attempted to report this through Antigravity’s built-in feedback mechanism, but the Submit button does not work.

I also tried disabling “Attach Antigravity server logs”, but that did not resolve the submission problem.

Therefore I’m reporting the issue here.

Request

Could the Antigravity team investigate whether there is a problem with the automatic OAuth/token handoff or Cloud Code authentication initialization in Antigravity 2.5.5, particularly the transition from successful Google authentication to:

cloudcode-pa.googleapis.com
daily-cloudcode-pa.googleapis.com
www.googleapis.com/oauth2/v2/userinfo

The fact that:

Google authentication succeeds in the browser,
manual “Try Another Email” authentication succeeds,
the Cloud Code endpoints are reachable independently,
and Antigravity can ultimately become logged in,

makes me suspect that the problem is occurring inside Antigravity’s authentication/service initialization rather than being a simple inability to reach Google.

I can provide sanitized auth.log, cloudcode.log, main.log, and network-shared.log files if required.

2

same problem here , but I tried manual try another email → login successfully → no responed and “click here” also no responed , can not jump back to IDE . so still login fail.

3

Hi Irena:

Found a solution that may work for you as well.

  1. Launch Antigravity.
  2. Let it authenticate.
  3. If authentication fails, I Do NOT click on the login button at the side.
  4. Instead, I click on the BLUE login button on the top right menu.
  5. Let authentication fails
  6. It will ask to log in with another email ID
  7. type in account ID.
  8. This time authentication success on the browser.
  9. Go back to Antigravity.
  10. Authentication successful.
  11. Click NEXT below right.
  12. Reach active agent mode.
4

hi Dja,

I’m having a Google authentication issue with Antigravity IDE 2.5.5 on Windows 11.

The login works correctly in the browser. Google confirms that authentication was successful, but after returning to Antigravity, the IDE remains on the login screen.

The Antigravity logs show:



Token exchange failed:
request to https://oauth2.googleapis.com/token failed,
reason: unable to verify the first certificate

I also see subsequent authentication errors such as:



state syncing error: key not found

I have already tried:

  • reinstalling Antigravity;
  • clearing the Antigravity user data;
  • Chrome and Firefox;
  • another internet connection;
  • checking that no proxy is configured;
  • verifying that the antigravity-ide:// protocol handler works.

I also tested HTTPS access to Google’s OAuth endpoint from Windows, and it works correctly.

Could this be related to Antigravity’s bundled Node/Electron runtime not correctly using the Windows certificate store? I saw your previous answer by finding the blue button but in my case there is no blue button because antigravity’s screen is still blocked in continue with mail without recovering the authentification wich is succeded from the browser and the button click here doesn’t work is there any solution??