Submit Watchkit Provisioning Error

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 the 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'

If you have further problems with provisioning. Try this link:

Technical Q&A QA1814
Setting up Xcode to automatically manage your provisioning profiles
Q: How do I configure my Xcode project to use automatic provisioning?
https://developer.apple.com/library/ios/qa/qa1814/_index.html

watchOS Provisioning Error

Possibly this is a bug with Xcode 7.0's automatic selection of provisioning profiles.

I solved this problem by setting each "release" provisioning profile at the target level:

code signing settings

Note: the default setting is "Automatic"

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'

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'

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".

Build Settings > 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'

Issue AppSubmit None of valid provisioning profiles allowed the specified entitlements Watchkit

This problem looks similar to this question.

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

and 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'

Regenerate Provisioning Profile

Provisining Profile error whatchkit

The bottom of https://developer.apple.com/watchkit/ says

Please Note: Apps built with Xcode 6.2 and iOS 8.2 SDK may be
submitted to the App Store. However, WatchKit extensions are not
accepted at this time.



Related Topics



Leave a reply



Submit