Bug Report: App Unresponsive After Web Login (BigInt Serialization Error)

Google Antigravity
1

Bug Report: App Unresponsive After Web Login (BigInt Serialization Error)

Issue Summary: The AntiGravity desktop app fails to process the login callback after a successful browser-based authentication. The application remains on the onboarding/login screen without any UI feedback, while the main process logs a fatal TypeError.

Environment:

  • App Version: 1.20.5

OS: Windows 11

Installation Path: C:\Users\xxxx\AppData\Local\Programs\Antigravity\

Technical Root Cause: The main process encountered an uncaught exception during the OAuth token migration or browser onboarding sync. The error is a TypeError: Do not know how to serialize a BigInt triggered by a JSON.stringify call. This suggests that one of the internal state objects (possibly a timestamp, large user ID, or workspace metadata) contains a BigInt value that is not being handled correctly before serialization.

Stack Trace Snippet:

Plaintext

[error] [uncaught exception in main]: TypeError: Do not know how to serialize a BigInt
at JSON.stringify (<anonymous>)
at vD (file:///C:/Users/xxxx/AppData/Local/Programs/Antigravity/resources/app/out/main.js:31:11765)
at nve.o (file:///C:/Users/xxxx/AppData/Local/Programs/Antigravity/resources/app/out/main.js:31:14636)
at nve.m (file:///C:/Users/xxxx/AppData/Local/Programs/Antigravity/resources/app/out/main.js:31:14511)
at wW.value (file:///C:/Users/xxxx/AppData/Local/Programs/Antigravity/resources/app/out/main.js:32:265)

Reproduction Steps:

  1. Launch AntiGravity App with LAST VERSION.

  2. Trigger “Login” which opens the default browser.

  3. Complete Google Authentication in the browser successfully.

  4. The browser onboarding server on http://localhost:10812 receives the request.

  5. The main process attempts to serialize the state/token, crashes internally, and the App UI remains idle.

2

This is a temporary workaround: [bug] serializer lacks a BigInt handler, causing unhandled JSON.stringify exception at runtime - #2 by pedrazadixon