Re: Code-signing oddness
Re: Code-signing oddness
- Subject: Re: Code-signing oddness
- From: James Moore <email@hidden>
- Date: Tue, 06 May 2014 22:39:51 -0700
We follow a similar approach but we do sign our main executables via the build settings. If you have to do Direct as well as MAS builds then the team selector will only cause you pain. For Developer ID signed apps leave the Team selector set to None and select “Developer ID Application” for the signing identity and “None” for the provisioning profile in build settings.
Signing Developer ID builds is the simplest case since it can’t involve any provisioned devices/capabilities.
James
Panic Inc.
On May 6, 2014, at 10:00 PM, Jerry Krinock <email@hidden> wrote:
> I was hoping someone would provide Shane an explanation, but apparently many are as confused as Shane, and myself, on the topic of Xcode signing with a Developer ID.
>
> My approach is to realize that the primary use case for Xcode nowadays is building apps for the App Store. Building for the Mac App Store is secondary, and building Developer ID apps is an edge case. Since codesigning is tricky, inconspicuous, and disastrous if not done correctly, I therefore do not trust Xcode to do this. In the Build Settings of my Developer ID apps, I set Codesigning to “Don’t Codesign”. My shipping script signs the product recursively using the codesign command-line tool, then assesses it with spctl, and halts shipping if it fails.
>
>
>
> _______________________________________________
> 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
_______________________________________________
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