Really not liking what I am seeing with macOS 15.1 and how it associates unsigned apps and packages as "untrustworthy and possibly full of malware".
Did an example with a simple audio plugin package, steps are:
1. Try to open the pkg and have it fail, **do not press "Move to Bin"**
2. Open System Settings, go to security and press "Open Anyway"
3. Click again "Open Anyway" in the new dialog
4. Input password
All this while screen is screaming "UNSAFE!" at you.
The "solution" to this is to pay Apple an $100 / year extortion fee (per developer), and also a bit of a convoluted setup to "sign" every single package you make (even automated ones in CI)
If Apple doesn't like you they can just stop accepting your builds. 🤷
ad-hoc builds don't work here, as signed apps are not allowed to load plugins (and libraries) that have been ad-hoc signed.
With this I might just drop macOS support from my projects.
@falktx Do it like Olaf Scholz and just get rid of what bugs you.