Skip to content

Troubleshooting

Ra1nify edited this page Oct 31, 2026 · 1 revision

Troubleshooting

Grouped by symptom. Each entry gives a check and a handling step.

Instance fails to launch

Core not installed

Overview shows core status Not installed. Install the core and retry.

Account held

A mutex conflict dialog appears. Two options:

Option Action Effect
Stop the owning instance Stop that process on the Instances page, then retry Unsaved work in the prior instance is lost
Force takeover Confirm the risk prompt The prior process is terminated and the lock is cleared

Project held

Same handling. The owner is recorded in RunningInstanceId in data/projects.json.

Port in use

An instance needs a local port. Close the conflicting process, or restart Gravityless to reallocate.

Material has no effect

Symptom: no Mica appearance, or the background is a flat color.

Check in order:

  1. The material option on the Appearance page is None;
  2. System transparency effects are enabled: Settings → Personalization → Colors → Transparency effects;
  3. The OS build meets the requirement listed in Appearance;
  4. HKCU\Software\Microsoft\Windows\CurrentVersion\Themes\Personalize\EnableTransparency is 1.

The material is drawn by DWM. If any check fails, DWM emits no backdrop.

Symptom: material unchanged after editing the patch.

Re-injection happens only when the stamp in utils.js differs from MicaPatchVersion. Increment that constant after changing the template. Restart an instance to apply.

Popup blur not visible

Symptom: menus and dialogs show no blurred background.

Check in order:

  1. Backdrop blur slider is 0;
  2. Popup transparency is 0% (popupAlpha is 1, the fill is opaque and hides the blur);
  3. The popup sits over an empty material area with no page content to sample.

backdrop-filter samples page content only, never the DWM material.

UI still shows English

Symptom: some Antigravity UI strings remain English.

Check whether the string is a key in locales/zh-CN.json.

Case Handling
Key exists but has no effect Restart the instance
Key missing Append the entry; key is the English source string
Key exists but is a fragment The page splits a sentence; add each fragment separately

Strings added by an Antigravity update do not enter the dictionary automatically.

Conversation not visible in another instance

Symptom: a conversation created in instance A is absent in instance B.

Depends on the project binding count:

Bound projects Behavior Handling
1 Whole-directory junction, two-way Should be visible at once. Check both instances bind the same project
≥2 One-way snapshot Instance A writes back on exit; instance B must restart to remount

Write-back requires the conversation workspace_uris to contain a bound project path. Otherwise the conversation stays in the sandbox.

Stale account lock

Symptom: an account shows In use while no matching process runs.

A crashed instance left the lock behind.

Handling: Force unlock on the Accounts page, or Force unlock all.

Icon not updated

Windows caches exe icons. If Explorer shows the old icon after a replacement:

  1. Close the app;
  2. Delete %LocalAppData%\IconCache.db;
  3. Restart explorer.exe from Task Manager.

Tray icons do not use the system icon cache. Restart the app after changing Assets\tray.ico.

Data locations

Check these first when diagnosing:

Path Content
<install>\data\instances.json Instance state
<install>\data\projects.json Project state
<install>\data\accounts.json Account lock state
<install>\core\resources\app\dist\utils.js Patch output and version stamp
<install>\core\resources\app.asar.stock Original package backup

See Data Layout.

Recovery

Case Handling
Patch corrupted Delete core\resources\app\ and unpack again from app.asar.stock
Core corrupted Uninstall the core on the Overview page and reinstall; data\ is kept
Config corrupted Delete the JSON file; defaults are rebuilt on restart

A JSON parse failure falls back to defaults and does not block startup.

Clone this wiki locally