v2.3.2
Quiver Release Notes
2.3.2
Patch release that fully fixes self-update wiping your library. If you updated from 2.3.0 via in-app update and lost your apps list, this release addresses the remaining packaging gap.
Self-update: stop shipping blank apps.json (fixes #1)
- What went wrong in 2.3.1: Updater preservation was added, but release zips could still include a blank
apps.jsonbecauseQuiver.csprojcopied it into publish output. Updating from 2.3.0 also used the old updater (no preservation) and could wipe your library once. - Fix:
apps.jsonis no longer published with the app. CI strips it from Windows, Linux, and macOS release archives before packaging. - Updater: Windows batch script hardened — preserved files skipped with reliable
if errorlevelchecks; success path no longer falls through subroutine labels. - Preserved on update:
apps.json,settings.json,games.json, andCache/(unchanged from 2.3.1).
Migration from 2.3.0 or a wiped library
- First hop to 2.3.2: Prefer a manual install (extract the zip, keep your existing
apps.json) if you are still on 2.3.0 or already lost your library once. - Recovery: Check
%TEMP%\Quiver_backup_*(Windows) or/tmp/Quiver_backup_*(Linux) from the day you updated — your oldapps.jsonmay still be there. - Installed game files on disk are usually unchanged; re-add entries from App Catalog if needed.
Close After Launch (from 2.3.1)
- Quiver no longer closes after a download completes or after dismissing a download error when Close After Launch is enabled.
- Quiver still closes immediately after a successful launch.
Testing and reliability
- xUnit runs serially for Avalonia headless tests (fixes CI/local test hangs).
GameDialogServiceavoids dispatcher deadlocks when no main window is present.- New packaging regression tests assert publish output and release workflow do not bundle
apps.json.
Other
apps.json.exampledocuments the library file format with a sample entry (not shipped in releases).