Problem with signing vst3 on xcode mac arm. Tried many things

I’m currently starting on Xcode on my m1 mac with projucer last version as well as last version of xcode.
I get the same error in all projects but even starting a new audio plugin project
I get error about codesigning and more.

error: Sandbox: codesign(44786) deny(1) file-read-data /Users/myname/Desktop/Projects/projectname/Builds/MacOSX/build/Debug/projectname.vst3 (in target ‘projectname - VST3’ from project ‘projectname’)

Running codesign --verbose=4 --force --sign - “/Users/myname/Desktop/Projects/projectname/Builds/MacOSX/build/Debug/projectname.vst3”

/Users/myname/Desktop/Projects/projectname/Builds/MacOSX/build/Debug/projectname.vst3: bundle format unrecognized, invalid, or unsuitable

I’ve tried many things so far:

  1. changed in the build settings user script sandboxing to no
    changed build to “release” mode 2,3,4.
    Added in target build
  2. "CODE_SIGNING_ALLOWED = NO
  3. CODE_SIGNING_REQUIRED = NO
  4. ENABLE_HARDENED_RUNTIME = NO
    4.2 ENABLE_HARDENED_RUNTIME = YES"
  5. Added custom run script to bypass the plugin copying to vst3 folder
    5.2 Deleted the copying script
  6. Changed rights in folder
  7. Cleaned Derived Data and Rebuild
  8. Changed code signing style to manual too
  9. Disabled App sandbox
  10. changed location of the folder
  11. Tried completely new projects with vst3 only

Not sure which way i should go now ??
Any idea would be really helpful :slight_smile:

  • Is this a new error? Were you previously able to build any project successfully? If so, do you have any idea what might have changed in the meantime?
  • Sometimes signing can be broken by backup services like iCloud and DropBox - if your build/project directory is currently in a directory managed by one of these services, try moving the project to a different directory that’s not automatically backed-up.

I think it may be icloud breaking it… I had the same issue out of the icloud folder but now it’s in icloud and i have it but maybe it was different stuff giving the same issue.
I just need to find how to redirect xcode and will report

Even tho i’ve moved the files out of icloud folder i still get this error>

error: Sandbox: codesign(47670) deny(1) file-read-data /Users/myname/Projects/ArpSeggs/Builds/MacOSX/build/Debug/ArpSeggs.vst3 (in target ‘ArpSeggs - VST3’ from project ‘ArpSeggs’)

error: 9 duplicate reports for Sandbox: codesign(47670) deny(1) file-read-data /Users/myname/Projects/ArpSeggs/Builds/MacOSX/build/Debug/ArpSeggs.vst3 (in target ‘ArpSeggs - VST3’ from project ‘ArpSeggs’)

Running codesign --verbose=4 --force --sign - “/Users/myname/Projects/ArpSeggs/Builds/MacOSX/build/Debug/ArpSeggs.vst3”
/Users/myname/Projects/ArpSeggs/Builds/MacOSX/build/Debug/ArpSeggs.vst3: bundle format unrecognized, invalid, or unsuitable

I’ve tried so many things tbh i’m lost. I disabled SIP, gave it full disc access, tried all variations of signing in the project build settings and target vst3 signing & capabilities

There still may be stuff in that folder (such as hidden files) that are breaking this. Open the Folder in Finder and then press Cmd+Shift+. to reveal the hidden files and delete anything you don’t recognize (perhaps make a backup copy of the folder first).

Yeah oddly enough i see none…

Btw it’s an error that is there from just starting the project from projuicer in xcode.
Maybe it’s the way i updated projuicer ?
Weirdly even on a new project it fail. Without anything else than the base build of projuicer

Potentially a distraction, but in this path:

“/Users/myname/Projects/ArpSeggs/Builds/MacOSX/build/Debug/ArpSeggs.vst3”

Are you using the " character or are you using the “ character to quote the path as a string? (This may be the forum translating " to “, not sure, but worth checking…)

i don’t think it’s that tbh
this is the character "

i still get the issue now… idk what to do

Should i delete the update manifest script basically ?

Already tried to set the “hardened runtimes” to NO for the VST3 Manifest project?