codesign

I eventually gave up as it seems it was unhappy about this:illed com.mycomp.app [pid 28331] because its use of the com.apple.developer.icloud-container-environment entitlement is not allowedBut why not? I'm using my Development profile (i.e. Adhoc beta testing as per your documentation as well) and I saw that Xcode added a this entitlement with the value 'Development', which should be allowed outside the store as long as I'm signing with my Development ID (note: not 'Developer ID', but instead my Mac Developer profile).This is quite frustrating. Our app uses CloudKit and I need to be able to beta test it. We can't seem to! Finally if I export as 'as a Mac Applicaiton', this works but then spctl says:MyApp.app: rejectedorigin=Mac Developer: SomeDeveloper (SomeID)Aaargh. When I hand this over to our beta testers, they say the app won't install until they switch off gatekeeper.Why Apple, why! Do you no longer test these frameworks with all the neat testing suites added to xcode? Completely baffling that while iO

I should add, even setting it to 'Development' causes it to not launch with a codesign error saying this entitlement is not allowed. WHY NOT!

hmmm...I tried moving the other unused certificate to another keychain...so Xcode won't get confused. It seems I can only delete the item from my local keychain right after a system restart. Once Xcode starts doing its automatic stuff....it brute force re-downloads the unwanted certificate and installs it in my keychain..making the multiple codesigning problem reoccur.Not sure how this extra developer id certificates got created...

Ended up removing my developer profile, going to my other mac and exporting it...then re-import it on the mac that was having the trouble...codesigning fine now. There still is the extra developer profile which can be confusing but i'll take what I can get.

Dear developer,We have discovered one or more issues with your recent delivery for MyApp. To process your delivery, the following issues must be corrected:Invalid Signature - The binary with bundle identifier 'com.mycompany.myframework' at path myframework.framework] contains an invalid signature. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). If you are certain your code signing settings are correct, choose Clean All in Xcode, delete the build directory in the Finder, and rebuild your release target.Once these issues have been corrected, you can then redeliver the corrected binary.Regards,The App Store teamThis is also happening to me with my app. I don't have a watchKit extension, just a dynamic framework that i created. My BitCode is off for all my targets as well, and I've tried to revoke and ge

I'm also experiencing the same error from spctl (internal error in Code Signing subsystem) with the only results being the original source code with the error text and this post, though my environment differs.I'm running Yosemite 10.10.5 and though codesign runs just fine and reports good results with --display and --verify, inspecting it with spctl is a no go. Trying to run the app will result in the typical This app is damaged and can't be opened. You should move it to the Trash. error message. Restarting has no effect.Edit: Apologies, didn't see that this was specific to a 10.11 category.

Quite often, it wouldn't give me a backtrace. I would get a message telling me that Xcode was corrupted and I should re-download. On doing this, I'd still get the same crash and same error.However - thinking it was somerthing to do with El Capitan and Xcode 7, I downgraded to Mavericks and Xcode 6.x.x only to get the same crash. But this time, I got a more meaningful trace and which pointed to the SDL2.framework being incorrectly signed. I fixed the codesign on the framework, ran Xcode again and everything worked (re-installed El Capitan and currently downloading Xcode 7 again).I'd suggest Xcode should give a meaningful error rather than just bailing if a framework has been incorrectly signed.