Sonarr for ARM on Mac fails to update, but Intel version is successful

Sonarr version (exact version): 4.0.14.2939
Mono version (if Sonarr is not running on Windows): n/a
OS: macOS 15.5 (Mac mini 2020 M1)
Debug logs: Sonarr update debug log
Description of issue:

When I go to System > Updates and click on “Install Latest”, after Sonarr “upates”, version 4.0.14.2939 is still installed and running.

If I download the 4.0.15.2941 ARM version, copy it to my applications folder (overwriting 4.0.14.2939), and run the terminal command to sign it, no problem.

If I download and install the Intel version 4.0.14.2939 (on my Mac mini 2020 M1 running Rosetta), when I go to System > Updates and click “Install Latest”, the update installs without a problem.

Log provided above was done on a “clean” install of Sonarr (i.e., I deleted ~/.config/Sonarr, installed and ran v4.0.14.2939, then went to Systyem > Updates > Install Latest).

Edit: also tested on a MacBook Air 2022 M2 with the same results.

The issue is the Sonarr binary is not signed due to the requirements of doing that for macOS (Apple gatekeeping that), so it fails to update when it tries to run the update process.

The issue is the Sonarr binary is not signed due to the requirements of doing that for macOS

This answer doesn’t make sense to me because:

  1. The Intel version of the Sonarr app updates without a problem when I go to System > Updates and click on “Install Latest”.
  2. The ARM version of the Radarr app also updates the same way without a problem.

If the problem were a a signing issue, shouldn’t those binaries fail as well?

Perhaps the requirements on the intel for signing are more relaxed or has been disabled, signed executables wasn’t always mandatory.

Radarr has the same limitation and does not sign either. Codesign main and update executable for macOS · Issue #4535 · Radarr/Radarr · GitHub