Skip to content

Flowntier v0.4.6 — kill_flowntier.cmd helper (NSIS hook fix didn't work)

Choose a tag to compare

View all tags
@Thatgfsj Thatgfsj released this 28 Jun 15:47
· 106 commits to main since this release
v0.4.6
547003d

Honest changelog

My v0.4.5 fix for the NSIS install conflict did not work. I added an installer.nsi with a customOnInit hook — it was included in the generated NSIS source (line 28: !include ...) but the contents were never inlined into the compiled binary. Tauri 2.x's NSIS preprocessor silently drops the include. I verified with grep -c 'FindProcess|customOnInit' target/release/nsis/x64/installer.nsi which returns 0.

v0.4.6 is the honest fix:

  • Removed the dead installer.nsi file and the installerHooks config key (which doesn't exist in Tauri 2.x — I made it up based on stale docs).
  • Added scripts/kill_flowntier.cmd — a small Windows CMD script that uses tasklist / taskkill to terminate any running Flowntier instance. Run this before re-installing.
  • Bumped version to 0.4.6 so the NSIS installer filename reads Flowntier_0.4.6_x64-setup.exe.

Workaround for the install conflict

Before running the v0.4.6 installer (or any v0.4.x):

:: Right-click the script and 'Run as administrator' if needed
scripts\kill_flowntier.cmd
:: Then run Flowntier_0.4.6_x64-setup.exe

The script:

  1. Checks if flowntier.exe is running via tasklist
  2. If yes, calls taskkill /F /IM flowntier.exe
  3. Waits 1 second for the OS to release file handles
  4. Prints confirmation and pauses

Real fix deferred to v0.5

The proper long-term fix is either:

  • Tauri's NSIS template to expose a real installer-hook API (file a Tauri issue if not already), OR
  • Switch to a WiX bundle (WiX has richer pre-install hooks but requires the WiX toolchain)

Both are tracked for v0.5. Until then, the helper script is the honest workaround.

Assets 3
Loading