redFrik
Signing did not work on Catalina
Hello Fredrik,
I had used your RedPhasor in a pseudo-UGen I 've made some years back and when I tried to run it it did not work. So I downloaded the new signed binaries but when I compiled SC I got a separate dialog for every single UGen! I would have to go to System Preferences and allow for every one of them. So I deleted everything apart for RedPhasor 1 and 2 and had to deal with 4 dialogs but of course that makes it very difficult for using it in projects intended for sharing as a Quark or otherwise.
I was ready to ask why not include them on the main sc3-plugins but after some googling I found this pull request. So it seems you had already done the work for this but did not get through.. 😕
hi Dionysis, happy to hear you like RedPhasor. sorry, i don't know much about signing binaries but i'll make some changes here and try to set up f0plugins to build and deploy with github actions ( https://madskjeldgaard.dk/posts/how-to-gh-action/ ) hopefully that will fix the problems.
ok, i restructured everything and these plugs are now being built with github actions. please the new release a go... https://github.com/redFrik/f0plugins/releases/tag/v4.0.3 hopefully the issues with signing binaries are solved.
Thank you for doing this! Unfortunately, I still got the flood of dialogs with "cannot be opened because the developer cannot be verified". In the end I had to remove everything apart from RedPhasor1 and 2 and then for each UGen: cancel -> go to system preferences -> allow -> reopen -> click on allow again and finally have them working. This whole signing architecture is giving me a headache. I am having related trouble with updating my sc_osx_standalone to 3.11 as well...
sorry, i'm as lost as you.
do you get the same problem with ... https://github.com/madskjeldgaard/mkplugins/releases or with these... https://github.com/supercollider/sc3-plugins/releases just trying to isolate the problem... if it's something i'm doing wrong or a more general problem for everyone.
I tried and I got the same from mkplugins. sc3-plugins does not have the issue though!!
i'm on Mojave and can run mkplugins directly and without any warnings.
in my System Preferences / Security & Privary i have allowed apps downloaded from 'App Store and identified developers'. and i tested with the 'signed, notarized' supercollider app downloaded from the official homepage.
I am doing the exact same thing but I am on Catalina.. All these issues are Catalina/Big Sur related. I don't think it is just me because in that case I would expect to also have the problem with sc3-plugins 🤷♂️
The sc3-plugins are signed. Probably I and everyone else building 3rd-party plugins will need to learn how to do that. :-( Sorry for the hassle this has caused you.