Velopack shortcut AUMID (velopack.Flaxative) differs from the client's (Forked.Flaxative) #544

Open
opened 2026-11-14 09:07:59 +00:00 by charles · 1 comment
Owner

Found while doing Daily use 27 (#516), commit 09ec967 on dailyuse-27-platform-notification-idle.

What: the Velopack install's Start-menu shortcut carries the AppUserModelID velopack.Flaxative, but the process (apps/fluxer/src/main.rs set_app_user_model_id) and, since Daily use 27, its toasts use fluxer_platform::WINDOWS_APP_USER_MODEL_ID = Forked.Flaxative.

Why: the velopack 1.2.161 SDK (locator.rs:301-314) takes the AUMID from the package manifest's shortcutAumid and otherwise uses velopack.<packId>. xtask/src/package/velopack.rs vpk_pack_args passes no custom AUMID, so the manifest has none and the shortcut gets velopack.Flaxative. Velopack's startup_hook also sets the process AUMID to that, before main.rs overrides it.

Effect: Windows shows toasts only for an AUMID that a Start-menu shortcut carries. Toasts raised under Forked.Flaxative may be dropped without an error (the notifier falls back to PowerShell's id only when WinRT reports an error), and taskbar pinning/grouping does not match the shortcut.

Fix (packaging): have vpk pack write Forked.Flaxative as the manifest's shortcutAumid (check the exact vpk 1.2.161 flag name), or make both use the same id. Then check on Windows hardware that a toast appears under Flaxative and a click raises the window (spec §14).

Steps to reproduce: install with the Velopack Setup.exe, read the shortcut's System.AppUserModel.ID (e.g. PowerShell (New-Object -ComObject Shell.Application) or Get-StartApps | ? Name -like 'Flaxative*'): it shows velopack.Flaxative.

Found while doing Daily use 27 (#516), commit 09ec967 on `dailyuse-27-platform-notification-idle`. **What**: the Velopack install's Start-menu shortcut carries the AppUserModelID `velopack.Flaxative`, but the process (`apps/fluxer/src/main.rs` `set_app_user_model_id`) and, since Daily use 27, its toasts use `fluxer_platform::WINDOWS_APP_USER_MODEL_ID` = `Forked.Flaxative`. **Why**: the `velopack` 1.2.161 SDK (`locator.rs:301-314`) takes the AUMID from the package manifest's `shortcutAumid` and otherwise uses `velopack.<packId>`. `xtask/src/package/velopack.rs` `vpk_pack_args` passes no custom AUMID, so the manifest has none and the shortcut gets `velopack.Flaxative`. Velopack's `startup_hook` also sets the process AUMID to that, before `main.rs` overrides it. **Effect**: Windows shows toasts only for an AUMID that a Start-menu shortcut carries. Toasts raised under `Forked.Flaxative` may be dropped without an error (the notifier falls back to PowerShell's id only when WinRT reports an error), and taskbar pinning/grouping does not match the shortcut. **Fix (packaging)**: have `vpk pack` write `Forked.Flaxative` as the manifest's `shortcutAumid` (check the exact `vpk` 1.2.161 flag name), or make both use the same id. Then check on Windows hardware that a toast appears under Flaxative and a click raises the window (spec §14). Steps to reproduce: install with the Velopack Setup.exe, read the shortcut's `System.AppUserModel.ID` (e.g. PowerShell `(New-Object -ComObject Shell.Application)` or `Get-StartApps | ? Name -like 'Flaxative*'`): it shows `velopack.Flaxative`.
Author
Owner

Reopened: the merge of #949 closed this automatically. The fix shipped in nightly 2026.1119.401 (Shell 42), but the check on a real Windows 11 install (docs/acceptance/shell.md, "Install check") has not been done yet. Close once that passes.

Reopened: the merge of #949 closed this automatically. The fix shipped in nightly 2026.1119.401 (Shell 42), but the check on a real Windows 11 install (docs/acceptance/shell.md, "Install check") has not been done yet. Close once that passes.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
charles/fluxer-native#544
No description provided.