Critical Bug: Persistent HTTP 400 "Invalid project resource name projects/" even after Gmail switch

[StevenX]

That really is the solution to the problem. I had to change my email address back to the one I used months ago when I signed up for the subscription and first started using Antigravatiy. Changing the email address for the Google account causes this error. That’s extremely poor on Google’s part. Is Google really unable to match these changes across all related products? Not to mention communicating this properly.

[Andrew_Deeley]

Are you on Pro or Ultra? I’ve been getting the same blank project ID error since the 11th Feb. I signed up to Antigravity Ultra using my own email @me.com address, worked perfectly until 11th Feb. Now every attempt to connect ends up in an HTTP 400 Bad Request. I don’t have a gmail alias associated to the account and so this fix won’t kickstart the backend auth for me.

[Mensekoftei]

I don’t have the option to change it back

[Leon_Wu]

@mattorq

I removed the gmail service from my google account and AG works fine again.
It seems the same happens to users who change their gmail address.

worked for me , really thanks

[shawn_hu]

I meet the same issue. But I only have one email account and it’s my gmail acount. so the upper trick doesn’t work for me. In my situation, I use antigravity for the first time without create a gemini api key. After I create a gemini api key (during this process, it also created a cloud project), this issue is fixed

[zane_aspeling]

No this didn’t work for me unfortunately, lucky you

[shifeng_lin]

Has there been a solution to this problem？

[apple_He]

worked for me , really thanks

[rolandchieniei]

I deleted Gmail, and antigravity works now. > After deleting it, I was asked to reactivate the service via SMS verification. > “Your phone number has been verified too many times.”

Goodbye, my Gmail. AND GOOD JOB, GOOGLE.

[2399_kismet]

Have you fixed the issue?

[Ray_Band]

Unfortunately, no. Obviously, the problem is that I unlinked the email from which the account was created and the subscription was purchased, but now I don’t have access to it. The problem is quite massive, but the support does not want to help in any way…

[Yi_Duan]

Trajectory ID: 14c5d787-5ddd-4cbd-bf9c-c19be…
Error: HTTP 400 Bad Request
Sherlog:
TraceID: 0xeedd908d9b9…
Headers: {“Alt-Svc”:[“h3=“:443”; ma=2592000,h3-29=“:443”; ma=2592000”],“Content-Length”:[“382”],“Content-Type”:[“text/event-stream”],“Date”:[“Fri, 06 Mar 2026 08:38:45 GMT”],“Server”:[“ESF”],“Server-Timing”:[“gfet4t7; dur=216”],“Vary”:[“Origin”,“X-Origin”,“Referer”],“X-Cloudaicompanion-Trace-Id”:[“eedd908d9b967348”],“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”
}
}

[zane_aspeling]

I GOT A FIX !!!, so my situation was the i replaced my @gmail address with @icloud address, that broke and gave me this error, all i did was add back the gmail following https://accounts.google.com/AddMailService and adding it gmail back and antigravity started working again didn’t even need to sign out and back in hope this helps, happy slopping

[love4taylor]

I upgraded my existing Google account to a custom domain email using the “Upgrade to Workspace” feature in Gmail Web, and then this error appeared. Right now I have no idea what’s going on, and I can’t follow the solution mentioned above either.

Trajectory ID: 
Error: HTTP 400 Bad Request
Sherlog: 
TraceID: 
Headers: {"Alt-Svc":["h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000"],"Content-Length":["382"],"Content-Type":["text/event-stream"],"Date":["Sat, 07 Mar 2026 16:07:22 GMT"],"Server":["ESF"],"Server-Timing":["gfet4t7; dur=338"],"Vary":["Origin","X-Origin","Referer"],"X-Cloudaicompanion-Trace-Id":[""],"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"
  }
}

[Patricio_Perez-Henri]

Trajectory ID: dc19cc02-1553-40bd-9664-2101c9e540e6
Error: HTTP 400 Bad Request
Sherlog:
TraceID: 0xbc998f34696cb50b
Headers: {“Alt-Svc”:[“h3=“:443”; ma=2592000,h3-29=“:443”; ma=2592000”],“Content-Length”:[“382”],“Content-Type”:[“text/event-stream”],“Date”:[“Sun, 08 Mar 2026 06:51:58 GMT”],“Server”:[“ESF”],“Server-Timing”:[“gfet4t7; dur=462”],“Vary”:[“Origin”,“X-Origin”,“Referer”],“X-Cloudaicompanion-Trace-Id”:[“bc998f34696cb50b”],“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”
}
}

[Thiago_Bhering]

Same HTTP 400 Bad Request error. The backend request is attempting to call a project with an empty ID: “message”: “Invalid project resource name projects/”.

This issue has been occurring consistently since versions 1.15/1.16 and remains fully present in the latest 1.20.4 update.

[DEFINITIVE PROOF OF SERVER-SIDE ROOT CAUSE] !!!
A secondary FREE Google account works flawlessly on the exact same machine, same network, and same Antigravity 1.20.4 installation. The issue is 100% isolated to my primary AI Pro account’s identity and its broken GCP auto-provisioning mapping.

[EXHAUSTIVE TROUBLESHOOTING ALREADY PERFORMED]
To completely rule out local cache, corrupt tokens, or conflicting aliases, I have performed the following destructive actions with zero success:

1. Complete clean uninstalls of the IDE (tested progressively from 1.18.x to 1.20.4).
2. Deep local cache purge: Deleted %APPDATA%\Antigravity, %USERPROFILE%.antigravity, and the VSCode %APPDATA%\Roaming\Code directories to ensure a sterile environment.
3. OAuth Token Revocation: Revoked all Antigravity and Google Auth Library accesses directly via Google Account Settings → Third-party apps & services.
4. Identity Purification: Removed my legacy third-party email alias (Hotmail) from my Google Account’s “Alternative emails” to force a clean authentication handshake, followed by a complete global logout and google.com cookie wipe.

Antigravity Version: 1.20.4
Date: 2026-03-06T21:51:18.942Z
Electron: 39.2.3
Chromium: 142.0.7444.175
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200

Status: INVALID_ARGUMENT
Details:

• “@type”: “type.googleapis.com/google.rpc.BadRequest”
• “description”: “Invalid project resource name”, “field”: “name”
• “message”: “Invalid project resource name projects/”

[Patricio_Perez-Henri]

This worked for me!!!

[NightFading]

Hi everyone,

I was facing the same persistent HTTP 400 error. I saw the suggestion about deleting the Gmail service, but since I use my Gmail for almost everything and have years of critical data, I couldn’t take that risk.

After some digging, I accidentally found a much safer solution that worked for me. It seems the issue might be related to “stale” account security info rather than the Gmail service itself.

My Case & Solution: I noticed that my Recovery Email in my Google Account settings hadn’t been verified since 2023. Even though it was already set up, it was just sitting there “unverified” for 3 years.

1. I went to Google Account → Security → Recovery email.

2. I followed the prompt to verify it (received the code in my backup email and entered it).

3. Immediately after verification, Antigravity started working perfectly! No more 400 error.

My Error Log (for reference):

Trajectory ID: 1a4d8263-58b0-41e6-a858-25e1f41f29fb
Error: HTTP 400 Bad Request
Sherlog:
TraceID: 0xa4082466a9489421
Headers: {“Alt-Svc”:[“h3=“:443”; ma=2592000,h3-29=“:443”; ma=2592000”],“Content-Length”:[“382”],“Content-Type”:[“text/event-stream”],“Date”:[“Wed, 11 Mar 2026 09:08:55 GMT”],“Server”:[“ESF”],“Server-Timing”:[“gfet4t7; dur=407”],“Vary”:[“Origin”,“X-Origin”,“Referer”],“X-Cloudaicompanion-Trace-Id”:[“a4082466a9489421”],“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”
}
}

If you are hesitant to delete your Gmail service, please try re-verifying your recovery email or updating your security info first. It might trigger the necessary identity sync to fix the Project ID mapping.

Hope this saves someone else’s time and data!

[shifeng_lin]

This method is ineffective for me

[NightFading]

Sorry to hear that it didn’t work for you. It seems this bug might have different root causes for different accounts. Hopefully, you can find another workaround soon!