Xcode 8 shows error that provisioning profile doesn't include signing certificate

Question

Xcode 8 shows error that provisioning profile doesn\'t include signing certificate.

This issue is with Xcode-8 only with Xcode 7, same provisioning profile showing r

Answer 1

In my case, in keychain i had two certificates with same name, i removed one of the certificate which is duplicate then it solved the problem.

Answer 2

You may also solve code signing issues with great Fastlane toolkit. Authors put a lot of effort to effectively automate building, signing iOS apps (and more).

So in the mentioned suite, there is tool sigh which magically resolves any signing issues, hence the name :) Nice thing here is, that this tool encapsulates a knowledge about common signing issues and can detect and resolve most of them.

Fastlane is installed as Ruby gem:

gem install fastlane

And then simply invoked:

fastlane sigh --development

Answer two questions, and voila:

[11:56:55]: No existing profiles found, that match the certificates you have installed locally! Creating a new provisioning profile for you
[11:57:01]: Creating new provisioning profile for 'com.myapp' with name 'com.myapp Development'
[11:57:06]: Downloading provisioning profile...
[11:57:09]: Successfully downloaded provisioning profile...
[11:57:09]: Installing provisioning profile...

Finally, go to Build Settings -> Signing, and switch to newly created provisioning profile, whose name you just saw in the command output.

This example is for development code signing problem (running on the device). Check sigh documentation for all other options.

Answer 3

For those who should keep using not auotamatic for some reason

Open keyChain Access to see whether there are two same Certifications ,If there's two or more,Just Delete to one and it will work :)

Answer 4

If you use manual signing (which I would definitely encourage), this error may occur because Xcode thinks that it should sign a release build with a developer certificate, which is obviously not included in a release provisioning profile.

There is a build setting that defines which certificate should be used for which build configuration. To change it, go to build settings and search for Code Signing Identity. When expanded, there should be separate rows for each build configuration (usually Debug and Release) with in the second column its selected identity (usually iOS Developer or iOS Distribution). Make sure that it's set to the correct identity for each build configuration.

In some cases, the build configurations can also be expanded. Make sure that also its subitems are set to the correct identities.

Answer 5

It means you need to do either 1 of the below:

1. You should have created a certificate at the Developer Center and then included that Certificate within the Provisioning Profile which you will Import into XCode.
2. Else, If you are using a certificate created by someone else, then get them to share/export their certificate & private key (.p12 file) to you & you need to include this into your keychain. Refer here

A solution to #2 when you are not able to get the certificate & .p12 file from the creator would be to just check the 'Automatically manage signing' option.

Answer 6

I got one of these emails from Apple:

Dear John Doe,

The following certificate has either been revoked by a member of your development team or has expired:

Certificate: iOS Development

Team Name: Honey Team, LLC

This does not affect apps that you've submitted to the App Store or your ability to update your apps. If you're using provisioning profiles that contain this certificate, they must be recreated before they can be reused. For details, see the "App signing overview" section of Xcode Help.

Best regards,

Apple Developer Program Support

---

I created a new certificate which revoked the previous certificate (locally and on any other developer's mac). For it to work I must download the new provision profiles.

The solution is to:

• login into Apple developer account
• remove/revoke the previous certificates created in my name.
• add the new certificate to the provision profile. You can identify the newer one by their expiry date
• download them again from Xcode. Xcode >> Account >> Download All Profiles
• restart Xcode

I personally didn't have such access. This access was only available to our team's admin, hence I don't have screenshots nor certain if these steps are 100% correct.