Hey @adsouza. I am on Apple M1 with MacOS Sonoma. If I remember correctly, you can still run the application by clicking somewhere on "Allow" within the permissions dialog of the system settings. @uspasojevic96 may maybe remember a bit better what the correct way was.

Other than that, I think, the only way to avoid users getting that dialog, is to pay Apple the fee to get a developer license to digitally sign the software with. That's it. - I tried it but failed, because it's apparently not that trivial. We want to have that eventually however. :)

You're referring to disabling protection system wide. That's not necessary. The workaround I described is nice and granular. Maybe just add it to the installation instructions for macOS?

The workaround I described is nice and granular. Maybe just add it to the installation instructions for macOS?

Oh that would be great. Thanks for the advice!

p.s.: sorry for the unclear description, I'm not a macOS-main user. I happen to use it, but i'm not confident enough to know it by heart. :)

@adsouza its related to signing and gatekeeper, not SIP

@christianparpart buy the developer account and sign contour already

@christianparpart buy the developer account and sign contour already

I actually tried, early last year, but failed in actually doing the signing procedure. In the end, it is our Github CI that must be able to sign the MacOS binary. I am actually open in paying that 80 bucks (or so) again (it sadly faded out just a week ago). Not sure if I'd be any better this time :)

There's a workaround for this that I eventually discovered but is worth documenting:
Right-click on the app in Finder, select Open; a popup appears, at which you can choose to run it.
After that it'll start normally.

This is completely normal for apps from developers without a subscription, it's not a "workaround", it's how MacOS ensures you've verified the app is not a trojan. I would change the name of the issue to reflect that it's just a suggestion to the devs to get a subscription again.

@christianparpart i understand that this was resolved by now and we sign contours build for macos? maybe @uspasojevic96 you know?

Signing works now, but we have some other issue currently where it still cant validate file

but this might be due to my machine setup. I hope other can verify. On the other hand, maybe I can pull off my old x86-MacOS at some point and see how that one reacts on the newly signed build. :)

I had the same issue when installing using brew just now on the latest release (Sonoma 14.4.1). If you just open the binary after install you'll get a popup with no option to "Open" and no instructions for how to open. You have to right-click on the binary file (in /Applications) and select open there, and then a different popup says something similar except there's also an Open button :)

@dfallman @adsouza I have been getting some help in understanding and creating a profile on the Apple Developer platform and associated it with our application's signature. I do not know how long it will take, but soon (in theory), macOS should not complain anymore but straight open it. 🙏