Re: Why can't XCode sign an app for distribution outside the app store
Re: Why can't XCode sign an app for distribution outside the app store
- Subject: Re: Why can't XCode sign an app for distribution outside the app store
- From: Martin Wierschin <email@hidden>
- Date: Fri, 19 Jun 2015 13:49:03 -0700
> I just posted a signed version of my app as an update and numerous users report Apple wants to block it because I am not an identified developer
I’ve run into situations where Xcode’s code signing / Organizer export yields bad results. Sometimes the problem is due to invalid build settings, or mismatched entitlements. Sometimes a nested framework or helper app is missing a sealed resource. Sometimes your particular app bundle structure violates Apple’s code signing guidelines.
It’s super frustrating, since the process is opaque and Xcode gives no indication that anything went wrong. In my opinion Xcode should never export an app that can’t be launched under default Gatekeeper settings, without at least a warning. I’ve filed a variety of radars on this, but I don’t think any have been closed.
To prevent this problem from ever ruining a build, my distribution process now always runs the following checks:
codesign --verify --deep --verbose=4 /path/to/your/product.app
spctl -a -t exec -vv /path/to/your/product.app
Their output may pinpoint the cause of your problem.
I hope that helps,
~Martin Wierschin
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden