You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Update failed: invalid updater binary format [v0.14.0, not latest] #1541
I searched existing issues and believe this is not a duplicate.
OS
Pop!_OS 24.04 LTS x86_64
ActivityWatch version
v0.14.0 (rust)
Describe the bug
When ActivityWatch starts (on login, for me), a window pops up ("ActivityWatch Update"). It seems to try updating, but fails at the end.
Steps to reproduce
Start ActivityWatch (from scratch)
Wait for updater to fail
Expected behavior
ActivityWatch gets updated (in this instance, to v0.14.1)
Logs, screenshots, or other documentation
Additional context
I am NOT on the "latest ActivityWatch release", precisely because of this. Sorry for lying on the checkbox earlier. I can't really check if the issue persists on the latest version, because I can't try to update from the latest version (there's no version to update to if you're on the latest). I am on the next closest version, though. v0.14.0
Hi there!
As you're new to this repo, please make sure you've used an appropriate issue template and searched for duplicates (it helps us focus on actual development!). We'd also like to suggest that you read our contribution guidelines and our code of conduct.
Thanks a bunch for opening your first issue! 🙏
Thanks for the report, and no worries about the checkbox.
Likely cause: that error is raised by the Tauri updater when the downloaded update isn't the format your install type expects. The v0.14.1 latest.json only has AppImage entries for Linux (linux-x86_64, linux-aarch64). If the app was installed from the .deb or .rpm, the updater falls back to the AppImage and rejects it at the install step.
How did you install v0.14.0 (.deb, .rpm, AppImage, or the zip)? That will confirm it. Until it's fixed, installing v0.14.1 manually from the release page should get you updated.
Fix is in #1542: harvest signed .deb/.rpm updater artifacts so latest.json grows linux-<arch>-deb and linux-<arch>-rpm keys. It needs to land before the v0.14.2 tag. Merge does not repair the published v0.14.1 manifest — the next tagged release is what unblocks in-app updates. Manual install of v0.14.1 from the release page remains the workaround until then.
Still useful if you can say: how did you install v0.14.0 (.deb, .rpm, AppImage, or zip)?
Thanks, that confirms the affected install type: the .deb installation is being offered an AppImage instead of a Debian package. Installing the v0.14.1 .deb manually is the workaround for now. I'll keep this issue open until the release containing #1542 is published and the Debian update path is verified.
Activity
github-actions commentedon Oct 25, 2026
Hi there!
As you're new to this repo, please make sure you've used an appropriate issue template and searched for duplicates (it helps us focus on actual development!). We'd also like to suggest that you read our contribution guidelines and our code of conduct.
Thanks a bunch for opening your first issue! 🙏
TimeToBuildBob commentedon Oct 26, 2026
Thanks for the report, and no worries about the checkbox.
Likely cause: that error is raised by the Tauri updater when the downloaded update isn't the format your install type expects. The v0.14.1
latest.jsononly has AppImage entries for Linux (linux-x86_64,linux-aarch64). If the app was installed from the.debor.rpm, the updater falls back to the AppImage and rejects it at the install step.How did you install v0.14.0 (
.deb,.rpm, AppImage, or the zip)? That will confirm it. Until it's fixed, installing v0.14.1 manually from the release page should get you updated.TimeToBuildBob commentedon Oct 26, 2026
Fix is in #1542: harvest signed
.deb/.rpmupdater artifacts solatest.jsongrowslinux-<arch>-debandlinux-<arch>-rpmkeys. It needs to land before the v0.14.2 tag. Merge does not repair the published v0.14.1 manifest — the next tagged release is what unblocks in-app updates. Manual install of v0.14.1 from the release page remains the workaround until then.Still useful if you can say: how did you install v0.14.0 (
.deb,.rpm, AppImage, or zip)?Debatable8 commentedon Oct 26, 2026
I installed it via the .deb package.
I'll install the new version manually, then
TimeToBuildBob commentedon Oct 26, 2026
Thanks, that confirms the affected install type: the
.debinstallation is being offered an AppImage instead of a Debian package. Installing the v0.14.1.debmanually is the workaround for now. I'll keep this issue open until the release containing #1542 is published and the Debian update path is verified.fix(release): harvest signed Linux deb/rpm updater artifacts (#1542)