It’s really important you delete all those stuck sessions from the folders and invalidate the API key on this Google Dashboard thingy. Took me also quite a while, as you can see, and multiple tries. Also, you get this very sketchy SMS stuff etc. it’s really broken, but with just enough tries and tricks you can make it “just” work. The sessions may break all the time any way and you need to restart the IDE once in a while. It’s quite annoying, but soemwhat works.
I just figured out a simple way -
- Uninstall Antigravity IDE
- Install the Antigravity 2.0 and IDE again
- Login into the Antigravity 2.0 (apparently login works there - atleast for me) then you’ll see the interface.
- type any prompt in the chat ( for ex - hello) then it’ll tell you to verify. click on that and you’ll see the QR Code. scan that from your mobile.
And that’s it you are done, now you can also login into the Antigravity IDE using the same account.
this works me as well. i used antigravity cli.
after login it should redirect you to verification, If not redirecting try cli.
Just make sure you don’t delete anything in .gemini or you basically nuke the whole implementations plans and the whole brain.
That worked! Thank you
Thank you so much bro
I was stuck in the same authentication loop, but I managed to fix it by resuming a pending update. Here are the steps that worked for me:
-
Press Windows key + R, type
%localappdata%, and press Enter. -
Locate and open the Antigravity Updater folder.
-
Inside, open the Pending folder and click to resume the pending update.
-
Once the update finishes, open Antigravity 2.0 and sign in.
-
Type a simple prompt like “hello” in the chat.
-
A verification scanner should appear. Scan the QR code with your mobile device to complete verification.
After following these steps, the IDE logged in successfully without the 403 error.
I may have found why my auth connection keeps getting lost all the time.
The Rust Analyzer was taking so much memory that it basically killed the background auth flow.
Once I disabled it, it seems like it’s not losing the auth any more.
Used to work just fine before the update though. So, I look at this more of a Google bug too.
/e Google needs Chaos Monkeys for Local Environments ^^
