Antigravity login issue continously getting 400 error

hey devs, can any one help me logging in into antigravity, i have tried logging into it with my email but when ever i am clicking on verify it is redirecting me to a website and on that i am getting 400 error

this is what all i got even i tried by relogging in but still the same result.
is this a mine side issue or something related to account or it is from google’s side.

2 Likes

I’m experiencing the exact same issue.
After clicking Verify in Antigravity, Google opens and returns a 400 Bad Request (malformed request).
Age verification is already completed, and the issue reproduces even on a fresh Windows VM with a clean Antigravity install.
This looks like a server-side or OAuth flow problem rather than a local setup issue.

1 Like

i found the solution for that , if you have any mail that has google ai pro then you can login to antigravity otherwise you can’t think …. cause i was trying to log in with a mail on which i don’t have google ai pro then i was getting 400 error but when i tried with another account that has google ai pro it logged in .. that why i think only google ai pro subs are allowed in antigravity

Yes, I have the same thing.… I don’t know what to do anymore. I have an AI Pro subscription, but I can’t log in to Antigravity. Then why subscribe?

I have two google pro accounts and I can’t verify them both.

1 Like

Hello,

A persistent 400 Bad Request error during the login flow typically indicates that the browser’s request headers (specifically the cookies) have become too large or corrupted for the authentication server to process. Please try the following steps:

  1. Clear Cookies and Cache specifically for google.com and accounts.google.com in your default browser.

  2. If you are using a strict VPN or privacy extensions (like ad-blockers) in your browser, they may be stripping required headers from the login callback.

Please let us know if clearing the browser data resolves the issue for you.

1 Like

I wasn’t able to make any prompts after I updated to the newest version. I cleared the cache for google com and restarted Antigravity. Works like a charm now. Thank you~!

1 Like

Trajectory ID: 8255ddc9-2fd6-43e9-9423-6461abb64a3e
Error: HTTP 400 Bad Request
Sherlog:
TraceID: 0x52091d2acb23f0cb
Headers: {“Alt-Svc”:[“h3=“:443”; ma=2592000,h3-29=“:443”; ma=2592000”],“Content-Length”:[“382”],“Content-Type”:[“text/event-stream”],“Date”:[“Thu, 12 Feb 2026 02:22:57 GMT”],“Server”:[“ESF”],“Server-Timing”:[“gfet4t7; dur=437”],“Vary”:[“Origin”,“X-Origin”,“Referer”],“X-Cloudaicompanion-Trace-Id”:[“52091d2acb23f0cb”],“X-Content-Type-Options”:[“nosniff”],“X-Frame-Options”:[“SAMEORIGIN”],“X-Xss-Protection”:[“0”]}

{
“error”: {
“code”: 400,
“details”: [
{
@type”: “type.googleapis.com/google.rpc.BadRequest”,
“fieldViolations”: [
{
“description”: “Invalid project resource name”,
“field”: “name”
}
]
}
],
“message”: “Invalid project resource name projects/”,
“status”: “INVALID_ARGUMENT”
}
}

This is the exact same error I am getting on my Pro account, it has been like this for 24 hours and I have no idea why. I don’t switch account and do everything by the ToS.

I get this also After clicking Verify in Antigravity, Google opens and returns a 400 Bad Request (malformed request).

Solved it by going to https://myaccount.google.com/ then third party account then removing antigravity from the list

Then login again from antigravity.

For me its work!

Trajectory ID: 0b8972c1-ebf7-49fa-96d4-b380eaf0c16a
Error: HTTP 400 Bad Request
Sherlog:
TraceID: 0xf3d5c4a18240af2f
Headers: {“Alt-Svc”:[“h3=“:443”; ma=2592000,h3-29=“:443”; ma=2592000”],“Content-Length”:[“382”],“Content-Type”:[“text/event-stream”],“Date”:[“Thu, 12 Feb 2026 15:32:20 GMT”],“Server”:[“ESF”],“Server-Timing”:[“gfet4t7; dur=508”],“Vary”:[“Origin”,“X-Origin”,“Referer”],“X-Cloudaicompanion-Trace-Id”:[“f3d5c4a18240af2f”],“X-Content-Type-Options”:[“nosniff”],“X-Frame-Options”:[“SAMEORIGIN”],“X-Xss-Protection”:[“0”]}

{
“error”: {
“code”: 400,
“details”: [
{
@type”: “type.googleapis.com/google.rpc.BadRequest”,
“fieldViolations”: [
{
“description”: “Invalid project resource name”,
“field”: “name”
}
]
}
],
“message”: “Invalid project resource name projects/”,
“status”: “INVALID_ARGUMENT”
}
}