[Feature Request/Bug] Auto-updater fails with "Code path doesn't seem to exist" when User Installer is installed on a non-C drive

Google Antigravity
1
  1. OS: Windows 11 / Windows 10
  2. App Version: Antigravity IDE (User Installer)
  3. Installation Path: Non-C Drive (e.g., F:\Program Files\Antigravity)

Currently, the official release only provides a User Installer. When a user modifies the default installation path during setup to install the IDE on a non-C drive (e.g., F:\Program Files\Antigravity), the background auto-updater breaks during the next update cycle.

The updater creates a temporary _ directory to extract the new version but fails to move the files to the root installation directory. It looks for the executable in the default Windows AppData directory instead of the actual custom installation path, throwing a Code path doesn't seem to exist error. This leaves the installation in a corrupted state, resulting in blank/broken Start Menu shortcuts and a split version layout.

Steps to Reproduce

  1. Download the User Installer for Antigravity IDE.

  2. Run the installer and change the destination directory to a non-C drive (e.g., F:\Program Files\Antigravity).

  3. Trigger or wait for an automatic background update.

  4. The update fails, popping up an Inno Setup error window.

Log Excerpts

vscode-inno-updater.log shows the path mismatch:

Jun 26 07:15:56.381 INFO Starting: C:\Users\<User>\AppData\Local\Programs\Antigravity IDE\Antigravity IDE.exe, false, Antigravity...
Jun 26 07:15:56.382 ERRO Bad arguments: Code path doesn't seem to exist: C:\Users\<User>\AppData\Local\Programs\Antigravity IDE\Antigravity IDE.exe

The installation directory gets stuck in this layout:

Plaintext

Directory: ...\Antigravity IDE\
├── _ /  <-- (New version files trapped inside)
├── unins000.exe
└── unins000.dat

Suggested Solutions

  1. Provide a System Installer (.exe/.msi): Release a standard System Installer that requests administrative privileges and is fully optimized for global installation paths like Program Files on any drive.

  2. Fix Updater Path Logic: If only the User Installer is maintained, please ensure the vscode-inno-updater backend strictly resolves the actual installation directory dynamically, rather than falling back to the hardcoded AppData\Local\Programs default Windows path.