BNC 2.13.4 macOS build blocked by Gatekeeper and crashes due to invalid code signature (Code 2, CODESIGNING)

[ardayesil@…]

Dear BNC Development Team,
I would like to report an issue with the macOS build of BNC 2.13.4.
On macOS 26.3 (Apple Silicon, M2), the application initially shows the system warning:
“bnc.app is damaged and can’t be opened. You should move it to the Trash.”
After manually removing the quarantine attribute, the application no longer shows the “damaged” message, but it immediately crashes on launch with:

Termination Reason: Namespace CODESIGNING, Code 2
Exception Type: SIGKILL (Code Signature Invalid)
The crash report also shows the bundle identifier as:
com.yourcompany.bnc

As a temporary workaround, I was able to run the application by re-signing it locally using:
codesign --force --deep --sign - /Applications/bnc.app

After applying an ad-hoc signature, the application launches and runs normally.
It appears the distributed macOS build may not be properly signed and/or notarized. On current macOS versions, this results in Gatekeeper blocking the application and the system terminating the process at launch.
Could you please confirm whether the macOS build is intended to be signed and notarized for distribution?
Best regards,
Arda Yeşil

[wiese]

Hi,
we do not have a developer ID so far. We might try with ​https://knowledge.digicert.com/tutorials/mac-os-sign-code-command-line in the mean time.

[wiese]

19. #206

[wiese]

Please download from ​https://igs.bkg.bund.de/ntrip/bnc, install and test. You have to run

xattr -cr /Applications/bnc.app

once before running the app.