Watchkit Extension - No Matching Provisioning Profiles Found

No matching provisioning profiles found for WatchKit extension when submitting to App Store

This problem looks similar to this question.
Submit WatchKit Provisioning Error

I had the same problem. Here is the solution that worked for me.

Technical Q&A QA1830 The beta-reports-active Entitlement Q: How do I resolve the "beta-reports-active" code signing error? https://developer.apple.com/library/ios/qa/qa1830/_index.html

I had to regenerate the "Distribution" Provisioning Profile that I was using to submit my entire app, before I included the WatchKit extension. Specifically, these steps fixed my problem:

I logged onto developer.apple.com, selected "Certificates, Identifiers & Profiles".

1. On the Certs IDs & Profiles website > Provisioning Profiles page, click the App Store profile.
2. Click 'Edit'
3. Click 'Generate'

Any Help Watch app extension no matching provisioning profile found?

Yes, I have faced this problem before. You will need to create three separate provisioning profiles:

1) The provisioning profile that you already have for your actual app.

2) Provisioning profile for the WatchKit target.

3) Provisioning profile for the WatchKit Extension.

The Bundle Identifier is different for your app, watch kit app, and watch kit extension. You will use that Bundle Identifier when creating these three different provisioning profiles.

Make sure that when you go to your Build Settings for each of these three targets, under Code Signing select the specific Provisioning Profile that goes with your Bundle Identifier (not Automatic).

Xcode6 error: No matching provisioning profiles found for application

There's a couple possibilities for your issue, but the main causes is what I got from experience as well as other SO answers.

1. Your certificate or profile is outdated, in which case you have to go and regenerate your profiles again. I had this problem before, but Apple has described (partially) this issue.

2. You haven't set your profile in the Build Settings/Code Signing area, along with the appropriate certificates. Verify your Team in General/Identity and ensure that your profile is properly set.

   From Xcode 5: Code signing entitlement errors (The image is a bit outdated, but its the same as Xcode 6):
   

3. You are using a beta version of Xcode.
4. @jaytrixz states: "I just removed Entitlements.plist in Code Signing Entitlements under Build Settings" which could possibly work. Be sure that your provisioning profiles are configured as well.

iOS codesign error No matching provisioning profiles found

On the general tab in project settings you will be getting a warning and a fix issue button right below "Team" click on that, xcode will take care the rest for you.

WatchKit Extension Provisioning Profile?

I had both of these problems when I created my WatchKit app.

(1) For your first problem: warning: skipping copy phase strip.

I found the solutions here:

Warning during archive App with iOS 8 Extension in Xcode 6

and here:

Xcode 6 Archiving and get a warning "Skipping copy phase strip ,binary is code signed" when add "share extension" to target

Specifically, here are the steps I used to fix the problem:

1. Start Xcode and open your project.

2. Select the blue project icon in the upper-left-hand corner.

3. In second column that contains sections: PROJECT and TARGETS,
   select your main target under the TARGETS section.

4. Select the “Build Settings” tab.

5. Scroll down to the “Deployment” section.

6. Find and expand the section called “Strip Debug Symbols During Copy”

7. Find the row called "Release".

8. Change the value from "Yes" to "No".

Deployment > Strip Debug Symbols">

(2) For your second problem: Failed to locate or generate matching signing assets
The solutions are here:

No matching provisioning profiles found for WatchKit extension when submitting to App Store

and here:

Submit WatchKit Provisioning Error

I had to regenerate the "Distribution" Provisioning Profile that I was using to submit my entire app, before I included the WatchKit extension. Specifically, these steps fixed my problem:

I logged onto developer.apple.com, selected "Certificates, Identifiers & Profiles".

1. On the Certs IDs & Profiles website > Provisioning Profiles page, click the App Store profile.
2. Click 'Edit'
3. Click 'Generate'

No matching provisioning profiles when Submitting App to App Store in XCode 7.3

Nothing worked for me except the following simple solution. What resolved the issue was manually setting Provisioning Profile for Debug and Release to the appropriate values, as opposed to choosing Automatic (i.e., set values to your development and distribution provisioning profiles) for each of my targets. I did this for the main app, today extension, watchkit extension and watchkit app. After that all works as expected. Thanks for everybody's contribution.

---

Related Topics