How to Archive with a Developer Certificate, Then Re-Sign It During Submission with a Distribution Certificate

Can I archive with a Developer certificate, then re-sign it during submission with a Distribution certificate?

The problem here is that when you originally archived it would have set the entitlements to be compatible with a developer profile, such as the get-task-allow set to true but you're re-signing using a distribution profile which requires get-task-allow to be false. Unfortunately it can't go and change the entitlements and so you get this problem.

I'm not entirely sure why Apple can't make it so that it can go and change the entitlements and do all the magic there. The code, resources, etc will all be the same after all.

What happens if I publish an iOS by signing it with developer, not distribution certificate?

Unless xcode does not explicitly override the signing certificate while archiving and submitting to app store, I think the published app is signed using developer certificate

It does explicitly override it. During the submission process, as the app is extracted from the archive and uploaded to the app store, a distribution profile is added to the app. You would not have been able to upload the app to the app store if you didn't have the right profile and entitlements.

Create ipa with no developer certificate for remote distribution

Your developer can surely create an ipa, even if you don't give him access to the apple credentials.

1. Generate Distribution Certificate from your Mac and Export it. (Guide)
2. Create Adhoc Provisioning Profile like this.
3. Send both these items to your Developer.
4. Say to your developer to follow the steps here after archive, in order to create final ipa.

Hope it helps!

How to re-sign an iOS app for App Store distribution?

I have saved a lot of time using the AirSign application (which was not available when I posted my original question).

---

Related Topics