I think it is a bug bby Apple because the issue happens only on macOS 10.13 – on 10.12 all plugins are still loading fine – and if it was a voluntary feature removal, they would have removed or changed the ‘Lower Security Settings’ dialog I guess.
I can still load AUv3 plug-ins without lowering the security settings. But any AUv2 plug-in (except apple’s plug-ins) will still show the above dialog - even if the sandboxSafe flag is set.
This could mean that the dialog now has a different function: basically it warns you when loading AUv2s?
Update: no it also appears on AUv2s which do not have the sandboxFlag set. This means that the dialog has really become useless. Looks like a bug.
Can anybody find an AUv2 that successfully loads but doesn’t have the sandboxFlag set?
OK. Adding the resourceUsage section mentioned here fixes the issue.
I’ll update the Projucer to add this when the sandboxFlag is not set.
Yep, just tried adding the flag and it breaks our copy-protection (which is the vendor I assume you are referring to).
Will have to try the resourceUsage section Fabian mentions.
If you are relying on mach ports to do the IPC communication then you’ll need to specifically list all the mach ports that you are using. See the tech note for more info:
OK. The fix for this will appear on develop with commit 9ab9b28 shortly. Anybody with an AU should re-save their .jucer file with the most recent Projucer on develop. This will ensure that your AU will still work with GarageBand.
Unfortunately, it relies on a different mechanism, for which there is apparently no current workaround. Thank you for the suggestion, though.
Apple has just pushed an update to GarageBand which seems to remove the need for the sandboxSafe and/or resourceUsage flags in the Info.plist. It appears @jpo was right, and this was a bug on Apple’s end.
Interesting! (But sooner or later they will require sandbox safe plugins, for security reasons this makes absolute sense.)
Currently, by default, the Projucer will save the AU with sandboxSafe disabled but with a resourceUsage section. I’m hoping that because sandboxSafe is disabled, GB will allow the plug-in to do anything even if the permission is not listed in the resourceUsage section. Can anybody who has a plug-in which relies on IPC (for example) test this with the new version of GB?
GarageBand after update to High Sierra solved?
Is there any news about this ? I’m working on Mojave, and GarageBand doesn’t load my plugin even after I set the sandbox-safe flag to enabled.
My plugins rely heavily on IPC, btw …
have you tried put the sandBox key to false as well ?
So, you have downloaded and installed the new macOS 10.13 High Sierra, after checking that most of your audio software and plugins are now compatible … and then it shows that Apple’s own DAW, GarageBand, is on any of your 3- Plugins cannot load rooting. We’re sure Apple will provide an update in the near future, so an upcoming macOS or GarageBand update might well be the best solution.

