It seems that builds which include dylibs can have issues building as vst3 now.
I think this is because the helper tries to run the plugin constructor before the files have been copied?
I’ve been including my dylibs using the “Custom Xcode Resource Folders” field in Projucer to copy them to the proper location (inside the app bundle), and set the @rpath to look there.
This works great for AU / AAX / Standalone, but not VST3.
Apparently the VST3 manifest helper tries to run the plugin before it has copied the resources.
Also, for some reason, this only fails in the release build. Can’t figure that out.
I should also note that I can, of course, get around this by adding the libraries to /usr/local/lib.
However, for reasons unknown to me, the final VST3 will then have to be resigned to scan/load properly, and only works on intel machines.