Mac VST3 and AU build fails - "Command PhaseScriptExecution failed with a nonzero exit code"

Standalone builds fine. When I try to build VST3 or AU, however, it fails with this message

/Users/finbar/Documents/GitHub/Drip-VST/Builds/MacOSX/build/Debug/Droplets.vst3: code object is not signed at all
In architecture: x86_64

/Users/finbar/Documents/GitHub/Drip-VST/Builds/MacOSX/build/Debug/Droplets.vst3: resource fork, Finder information, or similar detritus not allowed

Command PhaseScriptExecution failed with a nonzero exit code

I’m on JUCE v7.0.9 and XCode 15.2. Any ideas what’s going on? Much appreciated.

Try trashing your builds folder in the project directory!

Still no luck unfortunately. The error occurs even with new projects and the example projects.

If you use iCloud/Dropbox etc., these services sometimes add metadata to files that prevents them from being signed. If that’s the case, try moving your project directory to a different location that isn’t automatically backed up. You will need to remove the Builds folder completely after doing so.

I’ve had this a couple times. It is a super cryptic one. for me it was when i had circular dependencies. So there might be something that is causing the linker to fail.

1 Like

AHH this was it, thanks so much! :sweat_smile:

+1 Getting this intermittently on a couple computers. Usually without the detritus bit, script failing though.

Seems to happen less on the M1 with OS Sonoma, and almost constantly on the MBP with OS 12.

Happens mostly on the VST3 build, but occasionally on AU as well. Standalone is always fine.

Have cleaned / rebuilt but that doesn’t seem to help. No circular dependencies here, and the fact that it’s intermittently is really strange.

In the VST3 case, I have been able to copy the script command and run it manually (not a great solution, but works for now). The script in question is the manifest related one that is auto generated of course.

This fixed it. Thank you!

I managed to stop this by moving my project folder to the desktop. Deleting the project folder, then copying it back to the original place. I also turned off the Time Machine backup, at the same time. I’m not sure which one helped, but I don’t get that error any more. I think I also deleted the build folder.

For me trashing the project and doing a fresh git clone (and identical…) ended that saga.
Just saying mine was an iOS project.