Introduction

Xcode 8 introduced several improvements and features aimed at enhancing developers' productivity. However, it also brought a number of changes in the code-signing process that may lead to common issues. One frequent error developers encounter is: "Provisioning profile doesn't include signing certificate". This article aims to delve into this error, understand its root causes, and provide solutions.

Understanding Code Signing

What Is Code Signing?

Code signing is a security process that ensures the authenticity and integrity of an application. By signing an app, developers verify they are authorized to distribute the app and that it hasn't been tampered with since it was signed. This is crucial for iOS apps, given Apple's strict App Store policies.

Components Involved

• Provisioning Profile: Contains information about the app ID, certificates, and devices it's authorized to run on.
• Signing Certificate: A digital identity used to sign the app. It's tied to the Apple Developer account.
• App ID: A unique identifier for the application.
• Devices: The list of devices a development provisioning profile permits running the app on.

The Error Described

Message: "Provisioning Profile Doesn't Include Signing Certificate"

This error typically indicates a mismatch between the provisioning profile (used by Xcode) and the signing certificate(s) associated with it. The mismatch might be due to several reasons, including expired certificates, incorrect profiles, or wrong project settings.

Possible Causes and Solutions

1. Expired or Missing Signing Certificate

If the signing certificate expired or was deleted, the provisioning profile would not recognize it.

Solution:

• Check your Developer Portal: Access your Apple Developer account and verify that your certificates are active.
• Renew or create new certificates: Use the Keychain Access on macOS to request new certificates if needed. Ensure you export the private key and store it safely.
• Update the provisioning profile to use the correct certificate.

2. Incorrect Provisioning Profile

The profile might not be associated with the correct certificate.

Solution:

• In Xcode, navigate to Preferences > Accounts > [Your Account].
• Click on View Details... and ensure the provisioning profiles listed include the correct certificate.
• Refresh the provisioning profiles in the portal and download any updates.

3. Xcode Project Settings

Xcode 8 might have incorrect targets or identity settings configured.

Solution:

• In your Xcode project, go to the General tab for your target.
• Ensure the Team setting corresponds with your Apple Developer account.
• Check that the Signing (Debug/Release) sections use the correct provisioning profile and certificate.

4. Device Restrictions

The attached device might be excluded from the current provisioning profile.

Solution:

• Confirm that the device is added to your Developer account.
• Ensure the provisioning profile includes this device.

Example Configuration

Here's a step-by-step example of setting up the correct configuration:

1. Create a New App ID if you're starting a new project.
2. Generate a New Certificate:
   • Use the developer portal to create a new certificate.
   • Download and add it to your Keychain Access.
3. Create a New Provisioning Profile:
   • Choose the new App ID.
   • Associate the newly created certificate and include all desired devices.
4. Configure Xcode:
   • In the Signing & Capabilities section, select the new provisioning profile.
   • Ensure the team and certificate are correctly set.

Summary Table

Here's a summary of the key factors and solutions:

Conclusion

While encountering the "Provisioning profile doesn't include signing certificate" error in Xcode 8 can be frustrating, it primarily revolves around ensuring all parts of the code-signing process are in alignment. By understanding code signing's components and following the solutions provided, developers can resolve this error and ensure a smooth app development process.