Analysis and Solution for "No Matching Provisioning Profiles Found" in Xcode 7.2

Problem Background and Symptom Description

After upgrading from Xcode 7.1.1 to version 7.2, many developers encountered a common yet perplexing issue: despite having matching bundle identifiers for provisioning profiles and certificates properly stored in Keychain, Xcode persistently reported the error message "Your build settings specify a provisioning profile with the UUID 'some_number', however, no such provisioning profile was found." This phenomenon is particularly confusing because the identical configuration worked flawlessly in Xcode 7.1.1.

Root Cause Analysis

Through thorough investigation, this problem primarily stems from changes in Xcode 7.2's provisioning profile cache management mechanism. When developers upgrade Xcode versions, old profile caches may not properly interoperate with the new version's signature verification system. Specific manifestations include:

1. Xcode's internal provisioning profile database may contain outdated or corrupted entries
2. The association between certificates and provisioning profiles may be lost during the upgrade process
3. Xcode 7.2 adjusted its profile validation logic, causing previously acceptable configurations to now be considered invalid

It's noteworthy that when setting Provisioning Profile to "Automatic" and Code Signing Identity to "iOS Developer", the error typically disappears. This occurs because Xcode takes over profile management in this mode, automatically selecting available configurations. However, this approach sacrifices developers' fine-grained control over the signing process.

Systematic Solution Approach

Step 1: Clear Cached Provisioning Profiles

First, open Xcode Preferences (using shortcut ⌘+,), navigate to the Accounts tab, select the relevant account, and click the View Details button. In the opened interface, select all displayed provisioning profiles and remove them using the delete key. Note that in Xcode 7.2, these profiles are not completely deleted from the system but are cleared from Xcode's cache.

Step 2: Restart Xcode and Redownload Profiles

After completing the first step, you must completely quit and restart Xcode. This is necessary because Xcode's profile list update mechanism has latency issues, and changes may not take effect without a restart. After restarting, return to the same configuration interface and click the Download all button. This will redownload all defined provisioning profiles from the Apple Developer Member Center.

During this process, developers may notice some profiles prefixed with XC:, which are automatically generated by Xcode. Don't worry about these files, as Xcode will regenerate them when needed.

Step 3: Restart Again and Configure Code Signing

After downloading completes, it's recommended to restart Xcode once more to ensure all changes take full effect. Then navigate to your project's Build Settings and locate the Code Signing section. Here, developers can:

• Select appropriate development certificates and profiles for Debug configurations
• Choose distribution certificates and profiles for Release configurations
• Ensure each configuration's Provisioning Profile setting matches its corresponding Code Signing Identity

Technical Details and Best Practices

Understanding Xcode's code signing mechanism is crucial for avoiding similar issues. Code signing involves three core components:

1. Certificate: Digital identity proof stored in Keychain, used to verify developer identity
2. Provisioning Profile: XML file containing app identifier, device list, and certificate information
3. App Identifier: Unique application identifier registered in the developer account

The following code example demonstrates how to check provisioning profile validity in scripts:

#!/bin/bash
# Check mobileprovision files in current directory
for file in *.mobileprovision; do
    if [ -f "$file" ]; then
        # Extract UUID from provisioning profile
        uuid=$(security cms -D -i "$file" | grep -a1 "UUID" | tail -n1 | sed 's/.*<string>\(.*\)<\/string>.*/\1/')
        echo "Provisioning Profile: $file, UUID: $uuid"
    fi
done

This script uses the security command to parse .mobileprovision files, extracting UUID information to help developers verify profile integrity.

Preventive Measures and Long-term Management Strategies

To avoid encountering similar issues during future upgrades, consider implementing these preventive measures:

1. Export current code signing configurations as backups before upgrading Xcode
2. Regularly clean Xcode's Derived Data and Module Cache
3. Use version control systems to manage project build settings, particularly code signing configurations
4. Consider using Fastlane or similar tools to automate certificate and profile management

For team development environments, establishing a unified code signing strategy is recommended, ensuring all team members follow the same certificate and profile management procedures. This can be achieved through shared developer accounts or enterprise distribution certificates.

Conclusion

While the "no matching provisioning profiles found" error in Xcode 7.2 can be frustrating, it can be reliably resolved through systematic cache clearing and reconfiguration processes. Understanding Xcode's internal mechanisms for managing provisioning profiles, combined with appropriate preventive measures, helps developers maintain stable and controllable code signing workflows while benefiting from Xcode's new features. As Apple continues to update its development tools, staying informed about code signing best practices will become increasingly important.