Re: Codesigning pain, god it hurts!
Re: Codesigning pain, god it hurts!
- Subject: Re: Codesigning pain, god it hurts!
- From: Quincey Morris <email@hidden>
- Date: Tue, 17 May 2016 21:43:51 -0700
- Feedback-id: 167118m:167118agrif8a:167118s68g6KHq55:SMTPCORP
On May 17, 2016, at 21:14 , Graham Cox <email@hidden> wrote:
>
> but the resulting app itself crashes on launch with a codesigning issue, possibly because the entitlments don’t match the code signature (?). That was what set me on the path to trying to harmonise my various certificates, which in turn probably caused me to damage something. I’m not really any the wiser about the whole arcane process, but at least I’m back to square one.
From the 7.3.1 Xcode release notes:
> Resolved Issues
> Provisioning
>
> • Fixed the issue where disabling a capability in the Xcode editor would leave the associated entitlement still enabled in the app. You may need to re-download provisioning profiles with the updated capabilities list after disabling a capability.
> Xcode no longer copies most entitlements from the provisioning profile into the app's code signature at build time. Entitlements for Wallet, GameCenter (for OS X), Data Protection, and Push notifications are still copied from the profile. All other entitlements should be declared using the Capabilities tab in the Xcode project editor. (24771364)
>
> Note: If your app configuration is not yet compatible with the corrected entitlements behavior you can temporarily disable the new behavior using:
> defaults write com.apple.dt.Xcode WantsExtraKeysFor25642247 -bool NO
Maybe that’s the problem you ran into?
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden