Hello team,
I am writing to report a critical issue introduced with the recent Antigravity 2.x updates on macOS Sequoia (running on a Mac Studio Apple Silicon).
The native application completely fails to launch. At startup, a popup window appears stating a Language Server error, and the application cannot be opened or accessed at all.
After a thorough investigation by downgrading, I managed to isolate the root cause and find a temporary workaround.
Issue details:
- Environment: macOS Sequoia, Apple Silicon (Mac Studio).
- Symptoms: Absolute crash on startup. A popup window indicates a Language Server failure, completely blocking the user from reaching the main application interface.
- Root Cause: During the boot sequence, the v2.x engine attempts to initialize/write configuration profiles (such as ‘mcp_config.json’ inside `~/.gemini/`) or update components via ShipIt. This triggers an unhandled initialization exception or a permission conflict with macOS Sequoia’s background process security, causing the language server to crash instantly before the UI can even render.
Temporary Workaround that restores functionality:
1. Completely wiping the `~/.gemini/` and `~/Library/Application Support/Antigravity/` directories.
2. Downgrading to the legacy version 1.22.2 (which bypasses these new broken routines).
3. Flushing and locking the `~/Library/Caches/com.google.antigravity.ShipIt` folder to prevent the silent auto-update from breaking the client again.
Version 1.22.2 runs flawlessly “like a charm,” proving that the startup crash is strictly related to how the new v2.x local server initialization interacts with recent macOS security enforcement.
Please investigate the startup initialization of the native language server on newer macOS versions to resolve this blocking issue.
Thank you.