Auto-Update Fails with `TargetsNotFound` on Linux (x86_64)

[appleparan]

Summary

The auto-update process fails on Linux x86_64 when checking for updates on the stable and 'beta' channel. The updater returns a TargetsNotFound error for the targets linux-x86_64-deb and linux-x86_64.

---

Environment

• OS: Linux (x86_64)
• Package Format: .deb
• Update Channel: 1.4.0-beta4
• Custom CA Certificate: Present (/usr/share/ca-certificates/CUSTOM_CERT.crt)

---

Steps to Reproduce

1. Install the application on a Linux x86_64 machine.
2. Trigger the update check (either manually or on shutdown).
3. Observe the update failure in the logs.

---

Expected Behavior

The updater successfully finds and downloads the latest release for linux-x86_64 / linux-x86_64-deb on the stable and 'beta' channel.

Actual Behavior

The update check fails with the following error:

Update check failed on channel 'stable': TargetsNotFound(["linux-x86_64-deb", "linux-x86_64"])

or

Update check failed on channel 'beta': TargetsNotFound(["linux-x86_64-deb", "linux-x86_64"])

---

Logs

2026-03-10T10:20:52.119806Z  INFO backend_ai_go_lib::commands::shutdown: check_for_updates_with_channel: Checking for updates on channel 'stable'
2026-03-10T10:20:52.120033Z  INFO backend_ai_go_lib::commands::shutdown: Loaded custom CA certificate from: /usr/share/ca-certificates/CUSTOM_CERT.crt
2026-03-10T10:20:52.588002Z ERROR backend_ai_go_lib::commands::shutdown: Update check failed on channel 'stable': TargetsNotFound(["linux-x86_64-deb", "linux-x86_64"])

---

Possible Causes

• The stable / 'beta' channel release metadata does not include targets for linux-x86_64-deb or linux-x86_64.
• The update server's TUF (The Update Framework) repository may be missing the relevant target entries for this platform.
• The custom CA certificate is loaded successfully, so TLS connectivity is likely not the root cause.

---

Additional Notes

• The custom CA certificate is loaded without errors, ruling out SSL/TLS issues as the primary cause.

[inureyes]

It was due to the build timing issue. I'm sure it is resolved now.

[appleparan]

Sadly, it still happens even with 1.5.0