[bug] serializer lacks a BigInt handler, causing unhandled JSON.stringify exception at runtime

vD() (in out/main.js), the ipc message serializer, throws an uncaught exception when passed a BigInt value (this happens when the google account that is trying to be logged in requires additional verification).

the function handles undefined, string, Buffer, VSBuffer, Array, and integer number, but has no BigInt branch and values fall through to the JSON.stringify catch-all, which throws an error on bigints.



[main 2026-03-12T00:03:15.163Z] [uncaught exception in main]: TypeError: Do not know how to serialize a BigInt
[main 2026-03-12T00:03:15.166Z] TypeError: Do not know how to serialize a BigInt
at JSON.stringify ()
at vD (file:///C:/Users/Mira%C3%A7/AppData/Local/Programs/Antigravity/resources/app/out/main.js:31:11765)
at nve.o (file:///C:/Users/Mira%C3%A7/AppData/Local/Programs/Antigravity/resources/app/out/main.js:31:14636)
at nve.m (file:///C:/Users/Mira%C3%A7/AppData/Local/Programs/Antigravity/resources/app/out/main.js:31:14511)
at wW.value (file:///C:/Users/Mira%C3%A7/AppData/Local/Programs/Antigravity/resources/app/out/main.js:32:265)
at jt.C (file:///C:/Users/Mira%C3%A7/AppData/Local/Programs/Antigravity/resources/app/out/main.js:30:2348)

repro: any ipc call passing a BigInt value triggers this.

expected: bigint serialized gracefully Actual: uncaught exception crashes main process

suggested fix: add a bigint branch, or patch the json fallback.

3 Likes

I managed to resolve the login issue by modifying a core main.js file in Antigravity.

Steps to fix:

  1. Navigate to the location indicated in your logs: …/main.js:31:11765 (Line 31, position 11765).
  2. Locate the following code:
    JSON.stringify(t)
  3. Replace it with this snippet to handle BigInt serialization:
    JSON.stringify(t,(_k,v) => typeof v === "bigint" ? v.toString() : v)

This change should allow the login process to complete successfully.

This is a temporary workaround. If Antigraviti is updated or reinstalled, main.js will be overwritten and you will need to apply this change again. I hope Google addresses this issue soon so this manual fix isn’t necessary.

6 Likes

Thank you! It was so frustrating i tried so many times they even asked me to verify my account after successfully login in with this method