Critical Bug: HTTP 400 "Invalid project resource name projects/" after GMX to Gmail Migration

[Michael_Hagen]

Environment:

• Antigravity Version: Latest (reinstalled Mar 4, 2026)

• OS: Windows

• Subscription: Paid Google AI Pro / Antigravity Subscriber

• Account Type: Personal Google Account (originally @gmx.de, recently added @gmail.com alias)

Problem Description: Every request to the Antigravity agent fails immediately with an HTTP 400 Bad Request. The backend response indicates that the project resource name is empty (projects/), which points to a server-side provisioning failure triggered by my email identity change.

Latest Error Details:

• Trajectory ID: `ba76c692-327d-4178-ba2b-5e0…

• TraceID: `0x93d8b1d968…

• Message: Invalid project resource name projects/

• Status: INVALID_ARGUMENT

Troubleshooting already performed:

1. Fully uninstalled Antigravity and deleted local config folders (%APPDATA%/Antigravity and .antigravity).

2. Revoked and re-granted “Google Antigravity” permissions in Google Account Security settings.

3. Verified in Google Cloud Console that no active project or billing account is correctly mapped to the new Gmail primary identity.

4. Attempted manual project ID entry (antigravity-neu), which was rejected as “not supported/invited.”

Request: It appears my account identity is “split” between the legacy GMX ID and the new Gmail primary alias. Could an engineer please look into my TraceID and manually re-provision or sync my subscription project to my new primary Gmail identity?

Thank you for your help!

[chunduriv]

Hi @Michael_Hagen,

Welcome to the Forum,

When the primary email identity changes, the automated linking breaks resulting in an Invalid project resource name projects/ error, try:

• Find your original email in the Alternate emails section of your Google Account settings
• Click make this your google account email
• Re-login to Antigravity

This might help resolve the issue.

Regarding the account identity issue, please reach out to Google One Help.

[get_seth]

Thank you. I have been experiencing this issue for weeks. I was wondering when Google expects to resolve it.