This morning my code signing isn’t working.
I haven’t updated Xcode or OSX for months
The message I get is
/users/myname/Documents/Mac2014/myapp.app: cannot find code object on disk
In subcomponent: /Users/myname/Documents/Mac2014/myapp.app/Contents/Frameworks/MBS Real Studio Compression Plugin.rbx_2.dylib
Anyone have an idea what can be done to fix /cause that?
I can codesign a simple RTF file in the same folder.
I can see the file it implies is missing within the frameworks folder.
This is affecting builds from 2012,2013 and 2014
If I remove --deep from the command, it fails to sign the app itself with the same message.
Well, I compile current plugins using Xcode 5.1.1 on Mac OS X 10.9.4.
If you have current plugins and older Xcode to sign, it may not know about newer library formats.
What MBS Plugin version? What Mac OS X version? What Xcode Version?
Thanks Christian.
You’ve helped resolve this just by asking for the Xcode version. (Although the error message pointed to MBS, that was a red herring: looks like they were the first items to be considered for signing in the bundle)
It appears that Xcode has recently and silently updated itself.
In the process it removed the old path that I had as the first line of my script:
export CODESIGN_ALLOCATE="/Applications/Xcode.app/Contents/Developer/usr/bin/codesign_allocate"
That used to be essential as it wouldn’t sign without it.
When I launched Xcode to find the version (now 5.1.1), I had to authorise once again.
Looks like it wasn’t going to allow me to sign anything until I agreed to another set of terms and conditions.
Once Xcode 5.1.1 had been opened in this way to get the version number, the code sign still failed.
But removing the CODESIGN_ALLOCATE shown above (given the path was no longer valid) allowed the code signing to work.
Im not sure where it is getting the helper tool from now, but things appear to sign again.
Sometimes all it takes is someone asking a question to trigger another set of possibilities.
I’m happy that my plugins work correct