Skip to content

Troubleshooting Guide

tawroot edited this page Sep 26, 2026 · 1 revision

Troubleshooting & Common Errors

This guide provides definitive troubleshooting procedures for common Antigravity IDE and network errors.


1. License Error (#3501): "You do not have a valid license of this product"

Symptoms

When sending any prompt (even a basic "Hello"), the IDE returns:

You do not have a valid license of this product. Please contact your administrator to request a license... (#3501)

Root Cause

The core language_server binary was not found in the standard candidate paths during initial patching, or Antigravity was updated and reverted the machine-code patch. Running ag-cleaner doctor displays:

Core Engine CHECK Not Found

Resolution

  1. Locate your Antigravity binary installation:
    • Linux:
      find ~ /opt /usr -name "language_server" 2>/dev/null
    • macOS:
      find /Applications ~/Applications -name "language_server" 2>/dev/null
    • Windows (PowerShell):
      Get-ChildItem -Path "$env:LOCALAPPDATA\Programs" -Filter "language_server.exe" -Recurse
  2. Manually patch using the direct path:
    ag-cleaner patch core /path/to/resources/bin/language_server
  3. Restart Antigravity using ag-cleaner launch.

2. HTTP 429 Quota Exhaustion & Token Corruption

Symptoms

Model requests fail with HTTP 429 or "Quota Exceeded" even when your quota should be intact.

Resolution

Perform a surgical state reset. This clears corrupted token caches and network state cookies while strictly preserving all conversation trajectories and workspace settings:

echo "y" | ag-cleaner clean

3. "The stream was interrupted" & Middlebox DPI Drops

Symptoms

AI response streaming suddenly halts midway through a turn, displaying The stream was interrupted. Please continue the task you were working on.

Root Cause

Stateful firewall middleboxes and Deep Packet Inspection (DPI) systems silently drop idle TCP connections on Server-Sent Event (SSE) streams if no packets transit for a few seconds.

Resolution

  1. Always launch Antigravity using the smart launcher:
    ag-cleaner launch
    Or generate the permanent desktop shortcut:
    ag-cleaner create-launcher
  2. Ensure your proxy node has low packet-loss (< 1%) and an exit latency under 1500ms to Google edge services (daily-cloudcode-pa.googleapis.com).

4. HTTP 400: "User location is not supported for the API use"

Root Cause

Transient proxy tunnel reconnects or local DNS leakage caused the request to reach Google endpoints with an unsupported or flagged data center IP.

Resolution

  1. Verify DNS uses remote resolution by confirming your environment specifies socks5h://:
    export ALL_PROXY="socks5h://127.0.0.1:10808"
    export HTTPS_PROXY="socks5h://127.0.0.1:10808"
  2. Switch to a residential or clean European data center node (Germany, Netherlands, Finland) in your proxy client.