[Bug Report & Investigation] HTTP 400 "Invalid project resource name" potentially linked to Gmail service activation on existing Google Accounts

Google AI Studio
1

Dear Google AI Engineering Team and Community Members,

I am writing to share some findings regarding the persistent HTTP 400 Invalid project resource name projects/ error when using Antigravity, which many of us have been experiencing.

After extensive troubleshooting on my end, I suspect this might not be an issue with local configurations, but rather related to how Google Cloud automatically provisions Project IDs for accounts with specific identity structures—specifically, accounts that were created with a non-Gmail address and subsequently had a Gmail service added to them.

Here is the step-by-step testing process I conducted, which led to this hypothesis:

  1. Initial State (Error Present): My Google account (which uses a non-Gmail primary email but has a Gmail address activated on it) consistently receives the HTTP 400 Invalid project resource name projects/ error. The backend request payload shows an empty project ID.

  2. Test State (Working): I went to my Google Account Settings (Data & Privacy → Delete a Google Service) and temporarily removed the Gmail service.

    • Result: Upon restarting Antigravity, the HTTP 400 error immediately ceased. The tool functioned correctly, and it appeared a valid Project ID was successfully retrieved and utilized.

  3. Restored State (Error Returned): I then restored my Gmail service via accounts.google.com/addmailservice.

    • Result: The HTTP 400 error returned immediately upon trying to use the tool again.

My Error Logs (Captured during the “Restored State”):、

Trajectory ID: ee85b491-7e37-4ce3-9c23-......
Error: HTTP 400 Bad Request
TraceID: 0xc15d9a547bf59b68
Date: Fri, 27 Feb 2026 03:01:51 GMT

{
  "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"
  }
}

Hypothesis for Investigation:

It appears that the automated mechanism responsible for assigning or verifying the default Google Cloud Project ID for Antigravity fails to correctly map the ID when the Google Account has this specific “merged” identity structure (active Gmail service on a primarily non-Gmail account).

I have noticed similar discussions in the community (linked below) where account transitions seem to trigger this lock-out. I hope these reproduction steps provide a useful vector for the engineering team to investigate the provisioning logic.

Thank you for your time and continuous efforts in improving these tools. We look forward to a potential backend fix, as permanently deleting our Gmail services is not a viable workaround.

Related Community Discussions:

Best regards.