I am unable to run any Xcode projects - new or old. I think I messed up my certificates or profiles as I kept deleting and adding new versions but I have no idea how to fix this.
Any help would be greatly appreciated.
I am unable to run any Xcode projects - new or old. I think I messed up my certificates or profiles as I kept deleting and adding new versions but I have no idea how to fix this.
Any help would be greatly appreciated.
I think I messed up my certificates or profiles
That seems unlikely given that the error message is resource fork, Finder information, or similar detritus not allowed
. The codesign
tool has detected something weird in your app bundle and is complaining about it. Here’s how you can reproduce this problem by hand:
% mkdir -p "MyTrue.app/Contents/MacOS"
% cp "/usr/bin/true" "MyTrue.app/Contents/MacOS/MyTrue"
% mkdir -p "MyTrue.app/Contents/Resources"
% touch "MyTrue.app/Contents/Resources/test.jpg"
% SetFile -t 'JPEG' "MyTrue.app/Contents/Resources/test.jpg"
% codesign -s - -f "MyTrue.app"
MyTrue.app: replacing existing signature
MyTrue.app: resource fork, Finder information, or similar detritus not allowed
In this example the presence of the traditional Mac OS file type on the JPEG file is making codesign
grumpy, but it could be some other class of metadata, like a resource fork on an extended attribute.
Unfortunately there’s no easy way to get the path of the offending file, but you can try this:
% ls -R@ "MyTrue.app"
…
MyTrue.app/Contents/Resources:
total 0
-rw-r--r--@ 1 quinn staff 0 4 Nov 15:30 test.jpg
com.apple.FinderInfo 32
All of this stuff tends to be reflected in the file’s extended attributes, so you should look for a file with xattrs.
Once you know what file is causing the problem, you can work backwards to find out how it managed to get this cruft.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"