codesign

I agree thatxattr -rcis definitely the answer. I think the issue is heightened security with the latest version of the `codesign` command-line tool, which of course Xcode uses. I was attempting to codesign an AppleScript bundle using that tool, and got the same resource fork, finder information, or similar detritus not allowed error. I have signed this bundle for years with Xcode 7 or earlier, and macOS 10.11 or earlier, and never had a problem. I found that the bundle itself had these extended attributes: com.apple.FinderInfo com.apple.metadata:kMDLabel_55jrfjefwdbulgyssk2kuyqciyan old Perl script inside Contents/Resources/Scripts had these extended attributes: com.apple.FinderInfo com.apple.TextEncodingand finally the main.scpt file, also inside Contents/Resources/Scripts had these: com.apple.FinderInfo com.apple.ResourceForkOnly after I removed the extended attributes from all three items would `codesign` work.I've submitted Bug.27727935 to Apple regarding this issue - the error

This helped a lot. Same thing for me. XCode 8 beta 4 suddenly started complaining about this. Here is how I resolved it in details.The error was/Users/timevision/Library/Developer/Xcode/DerivedData/MyApp-fwnvtcqqgyeoaqbsvmfeuzvjiqdg/Build/Products/Debug-iphoneos/MyApp.app: resource fork, Finder information, or similar detritus not allowedSo basically do the followingcd /Users/timevision/Library/Developer/Xcode/DerivedData/MyApp-fwnvtcqqgyeoaqbsvmfeuzvjiqdg/Build/Products/Debug-iphoneos/MyApp.appls -al@ *This will display any file that has extended attributes set. Look for any file that has @ at the end of the attributes. Mine was,-rw-r--r--@ 1 timevision staff 9014 Aug 6 22:12 AppIcon20x20@3x.png com.apple.FinderInfo 32 com.apple.metadata:_kMDItemUserTags 42Then I remembered adding this bloody new AppIcon in photoshop recently. Going back to my Images.xcassets/AppIcon.appiconset path I saw the file indeed has the extended attributes set.Then I used xattr -c * cmd to clear all extended attributes for the icon

The following is for Xcode 7.3.1:Create MyApp project.In the project build settings, set Strip Debug Symbols During Copy (COPY_PHASE_STRIP) to No.Set up the MyApp target’s code signing in the usual way: set Signing and Team ID in the General tabenable App Sandbox via the Capabilities tabCreate a MyTool target within the MyApp project.In the MyTool group, create a property list file called MyTool.entitlements.In that file, add to entries:com.apple.security.app-sandboxcom.apple.security.inheritboth as Booleans with the value set to YES.IMPORTANT Do not add the file to any targets.In the MyTool build settings, set Code Signing Entitlements (CODE_SIGN_ENTITLEMENTS) to MyTool/MyTool.entitlements.Build the tool.In the MyApp target, create a custom Copy Files build phase and: set Destination to Executablesadd MyTool to the list of items to copymake sure Code Sign On Copy is checkedBuild the app.Now check the entitlements of each item. First, the tool before it was copied into the app.$ codesign -d --entitle

Are these the .entitlements file or the output from codesign? They look like the former (because they’re missing a bunch of keys that I’d normally expect to see in the output from codesign), which is not good because you really need to check the entitlements of the built binary. Take another look at Debugging Entitlement Issues. It’d also be helpful if you answered the other questions from my previous post.Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Thanks eskimo! Your last reply solved the last bit of my puzzle.I want to explain why I asked this question after you replied to my other thread. Actually it's simple and common for a new user and an expert. An expert knows everything and many times he does not know why a new user asks a question; and a new user is always drowned in an expert's answers though he only needs one or two very stupid tips which an expert would always ignore because they are too 'obvious'.The 'stupid' tips I needed were:1. The commandline syntax for signing a binary tool. Believe it or not, I spent seveal hours to figure out 'codesign -s --entitlements'.2. Why I could not run the signed tool, which is obvious to me now. When I first encountered this error, I thought I must have done wrong in codesign process.BTW, I have submitted my app to App Store and everything works as before.

YES!! THANK YOU!I lost several hours to debugging this today. After updating our iOS app to Swift 3 and Xcode 8.0b6, all Keychain accesses in our application were failing during unit testing, on a real device or in the simulator. I nuked all codesigning stuff from orbit, rebuilt it all manually, nuked it again and let Xcode try its automagic mode, and repeated this with various build settings tweaks... nothing worked and the app couldn't be tested.And, because of the insane multi-year legacy of the Keychain error -34018, there are tons of red herrings and unrelated threads on the interweb tubes, and rabbit holes to go down.But, eventually I got to the end of this thread, and saw your tip to enable the Keychain Sharing entitlement for the main application being tested.Et voilà. Xcode can run all the automated tests that involve the Keychain (SecItemAdd(), SecItemDelete() and friends...) and they all now work, rather than returning errSecMissingEntitlement (-34018).So, thanks to your comment, my proble

Just FYI, I ran through this process on my machine (OS X 10.11.6, Xcode 7.3.1, standard Developer ID) and it worked fine for me. So AFAICT there’s nothing fundamentally broken here.What version of Xcode are you using?if I do codesign -dv myapp.app it comes back as myapp.app : no signature and TeamIdentifier=not set etcPlease post a copy of that output.Share and Enjoy — Quinn “The Eskimo!” Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Yeah, I had to convert the whole thing to Swift 2.3 to get it to build. I'm guessing they just changed Swift between making the project and beta 6. I uploaded the version I have been using to GitHub, feel free to suggest any changes to make it better. Please note, you still need to go into each target and select your team from the provisioning drop down to allow it to run on devices (a provisioning profile is required for device codesigning).https://github.com/brendancboyle/IceCreamBuilder-Fixed