there is nice tutorial from JUCE about creating installation packages for your plugins:
But there is nothing about permissions, privileges etc.
My client has serious problems on Catalina with installation of my plugins. Especially with VST3.
I am going to present those problems from little painful to most and unacceptable problems:
At first, while launch the PKG file there is prompt about unknown developer. As I know from my own experience it is quite standard and known issue with almost all applications from outside of Appstore. And I don’t even treat that as a problem. But it would be nice to remove such prompt and necessity to launch pkg file with right click etc. Don’t you know with whom should I speak from Apple to get any certificate or anything that allows my clients to avoid such not nice prompt at welcome?
But here the problem is bigger. Right clicking the PCK file and allowing to install is not enaugh. My client still need to go to System Preferences->Security & Privacy->General to allow to launch PKG file. And this is much more unpleasant.
Much worse thing is: even installation is successful, my client AGAIN need to go to System Preferences->Security & Privacy->General, this time to allow VST3 file to be launched.
And the worst thing and UNACCEPTABLE is that although my client give all of those Security permissions he still is not able to launch the plugin in Reaper. Reaper says “The vst3 plugin is not responding etc…” Because I don’t have such problems I can’t test it to find solutions.
But I have some observations.
While creating PKG file in OSX Packages app, there are planty of options to choose group and owner. And there are some “bit” settings like “setUID”, “setGID” or sticky. I wonder if I could avoid such problems by appropriate settings in Packages.
By default my plugins go to:
And in Packages app the default owner and group settings look like that:
While for myPlugin.aaxplugin the Group is set to Admin instead of Wheel.
What is worth to be mention that from few days I have PACE Eden Tools. But I use it only to sign the aaxplugin. Maybe I should also try to sign component file, vst3 file or even pkg file? Don’t you know if it could help? I want to prevent tests on my client side, that’s why I am asking here.
For any help great thanks in advance.