My personal Gmail account is unable to sign in to Google Antigravity / Antigravity IDE.
The error message says:
“Sorry, this account is ineligible to use Antigravity”
It sometimes also shows:
“Authentication failed”
or:
“not currently available in your location.”
This is a personal Gmail account, not Workspace. I am also a paid Google One / Google AI Pro subscriber. Gemini and other Google AI features work normally on the same account. The account profile address and current IP are both in the US, and the account is over 18.
This is materially affecting my ability to use the benefits associated with my paid subscription. Could someone please check whether this is an Antigravity account-level eligibility, entitlement, or location-association issue?
I can provide the affected Gmail account privately.
Sadly, no. I still haven’t received any meaningful response from the in-app issue report, Google One support, or this forum.
So far, there has not even been a simple official acknowledgement like “We’re looking into this.” The issue is still affecting my paid Google One / Google AI Pro account, and I’ve had to use other coding tools in the meantime.
I hope the Antigravity team can at least acknowledge whether this is an account-level eligibility or entitlement issue.
Antigravity requires users to be at least 18 years old. Access will be restricted if the Google Account’s date of birth is set to under 18 or if age verification has not been completed. Please verify the date of birth within your Google Account settings and ensure any pending age verification procedures are completed.
I have checked the affected Google Account, and it meets the age requirement. The date of birth on the account is set to an age over 18, and I do not see any pending age verification request or warning anywhere in the Google Account settings.
Also, Gemini and other Google AI products work normally on this same Google Account. I have not received any age-related restriction or verification prompt from any Google AI product other than Antigravity.
One additional point: this Google Account itself has been registered and active for well over 18 years, so it does not appear to be a newly created or underage account.
Could you please check whether Antigravity may be reading a stale or incorrect age-verification / eligibility signal for this account? The issue seems specific to Antigravity, not to the Google Account’s general age eligibility or access to Google AI services.
I encountered the same problem yesterday when I wanted to see what Antigravity 2.0 was all about. I hadn’t used Antigravity for a couple of months—at all.
I installed it on a new, clean server. I got the same error immediately upon authorization, then it changed to a completely incomprehensible one.
But the worst thing was that the built-in error message sending didn’t work. I filled in the details, took screenshots, allowed logs to be added, and so on. Nothing helped. Sending data didn’t work when I pressed the button.
Country: Estonia, Pro plan
Once again, I’m frustrated…
There is another personal Gmail account in the same Google family group. That family member account has signed in to Antigravity before and it can still sign in successfully now.
However, the Google family plan manager account is the affected account. That account previously used Antigravity on the free tier for about one month, and later became the Google One / Google AI Pro family plan manager account. After that, the family manager account can no longer sign in to Antigravity, while the family member account still works.
So this does not look like a device, network, Chrome, or general Google AI availability issue. It seems specific to the Antigravity eligibility / entitlement state of the family manager account.
Yes, the affected family manager account is my primary Google account in Chrome. It is the account I use daily, and it is the primary account for Gmail and Gemini. The account has been registered and active for around 20 years. Gmail, Gemini, and other Google AI products all work normally on this account.
I’ve submitted in-app issue reports in both Antigravity and Antigravity IDE, sent emails to the Google AI / Antigravity support channels, and posted the issue here as well. So far, I haven’t received any meaningful response or working solution.
The only reply I’ve received was here, but it suggested checking age verification, which does not seem to apply in my case. My affected account meets the age requirement, works normally with Gmail, Gemini, and other Google AI products, but still cannot sign in to Antigravity.
It seems like an Antigravity-specific account eligibility / entitlement issue, and it would be helpful if the team could at least acknowledge whether they are investigating it.
As far as I can understand antigravity has issues when the logged account (the antigravity account) is NOT the /0/ account in chrome (the one that when you go to gmail it enters as a /u/0).
From What I understand, you /u/0 is your old 20yo account and the antigravity account is another account (part of a family plan, but it does not matter, its a different account)
Just to clarify: the affected Antigravity account is actually my old ~20-year primary Google account, and it is also my primary account in Chrome / Gmail / Gemini. When I open Gmail, this account is the main account I use daily.
The other family member account is not the affected account. It is only relevant because that account can still sign in to Antigravity, while the family plan manager account cannot.
So in my case, the issue does not seem to be that the Antigravity account is different from the Chrome /u/0 account. The affected account itself is the primary account, works normally with Gmail, Gemini, and other Google AI products, but Antigravity still blocks it with an eligibility/location error.
I encountered a 403 error while using Claude Opus 4.6 in the IDE with the Ultra plan. I also filed a complaint with the One team (simply because Gemini and the IDE have no dedicated support department). But honestly, I didn’t have high expectations to begin with.
Throughout the entire communication process, the support staff only walked me through how to reinstall the IDE and how to log out and log back in.
Then came the age verification request — specifically, confirming I’m 18 or older. Yes, a strange requirement I’d never come across before. They sold me the $250 Ultra plan, took my money, and then when I ran into an issue, they turned around and asked: “Um, are you 18 yet?”
What is the point of that question? Does the Claude Opus model require users to be 18 while Gemini doesn’t? And if a user is underage, Google should return an appropriate error code — not a 403 (Server Busy).
Next, they asked me to record a video of the error occurring and to provide my payment information.
I even shared a link to a group showing that many other users were experiencing the same issue.
At that point, everything fell into an infinite loop with the default response: “We have escalated your issue to the relevant department and will get back to you once we have an update.”
I’m fairly certain my issue will never actually be looked at or resolved.
I’m sorry you’re dealing with this too. Your experience sounds very similar to mine.
What worries me most is that these issues affect paid Google One / Google AI Pro / Ultra users, but the support path still feels very disconnected. Google One support can discuss subscription and billing, but they don’t seem to have enough visibility into Antigravity / IDE account eligibility, model routing, or backend error states.
In my case, the suggested checks were also mostly generic: reinstall, sign out and back in, verify age, etc. But the affected account already meets the age requirement, works normally with Gmail, Gemini, and other Google AI products, and the issue only happens in Antigravity.
I agree that the error handling is confusing. If this is an age, entitlement, quota, model-access, or backend eligibility issue, the product should return a clear and accurate error message instead of vague messages like “ineligible,” “location,” “authentication failed,” or a 403-style error.
At this point, I think the most useful thing would be for the Antigravity team to acknowledge whether these are known account-level eligibility / entitlement / model-access issues and provide a real escalation path for paid users.
I spent weeks searching everywhere for a fix, but to no avail.
In another similar thread, someone mentioned that certain early-stage accounts may have been flagged. This means that any requests from these accounts through the IDE have a high chance of being redirected to an error code — a form of anti-abuse policy.
The best solution, apparently, is to switch to a different account.
The sad part is that I don’t want to switch. Since the beginning of the year, my account has spent over $3,000 USD on Gemini’s API through AI Studio.
Yes, at this point all of these explanations are only speculation.
It could be an account-level flag, an eligibility / entitlement sync issue, an age-verification signal, a regional check, an anti-abuse policy, a model-access problem, or something else entirely. But the real problem is that affected users have not received even the most basic explanation from the Antigravity / Google AI team.
Many of us are paid Google One / Google AI Pro / Ultra users. Some accounts can sign in but cannot access certain models. Some accounts cannot sign in at all. Some users get “ineligible,” some get “location,” some get “authentication failed,” and others get 403-style errors. These all look different on the surface, but they may be related to the same backend eligibility or entitlement system.
Telling users to switch accounts may be a temporary workaround for some people, but it is not a real solution. Many of us have long-standing primary Google accounts, payment history, API usage, subscriptions, family plans, and existing workflows tied to those accounts.
What is most frustrating is not just the bug itself. It is the lack of acknowledgement. So far, affected users have had to guess the cause by comparing forum posts with each other, while the official channels provide little more than generic reinstall / sign-out / age-verification suggestions.
At minimum, the Antigravity team should clarify whether this is a known account-level eligibility / entitlement / anti-abuse issue, and provide a proper escalation path for paid users.
Is there any official support path for Antigravity account issues?
It has been more than 2 weeks since I reported this issue through the in-app issue report, Google One support, and this forum, but I still have not received any meaningful response or workaround.
The affected account is a paid Google One / Google AI Pro account. It works normally with Gmail, Gemini, and other Google AI products, but Antigravity still blocks sign-in with eligibility / location / authentication errors.
Could someone from the Antigravity team please confirm whether this issue is being tracked, and whether there is a proper escalation path for paid users who cannot access the product?
Sorry, actually it has been more than three weeks, which is honestly surprising considering Google’s scale and all its public claims about “leading in AI.”
