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.

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. 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): You are using a beta version of Xcode. @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.

As jaytrixz, wrote in the comments...

"I just removed Entitlements.plist in Code Signing Entitlements under Build Settings "

I did the same and it worked after an hour of trying other things!

There are a lot of answers here, some have worked for me in the past, but not this time. I'd even created a new provisioning profile but that still did not help. Based on the "None of the valid provisioning profiles allowed the specified entitlements" part of the error I tried the following on a hunch and it worked for me:

1. add and remove a particular Capability

Go to Targets > Capabilities, and turn one on and then off. I doubt it matters which you choose, I added "Push Notifications" (which I don't need for my app), once it was "ON", I changed it back to "OFF"

https://i.stack.imgur.com/qG1U6.png

2. Archive again

I am now successfully uploading my app to the store.

Another solution, that fixed this symptom for me, can be found at: Xcode Watchkit: None of the valid provisioning profiles allowed the specified entitlements: beta-reports-active, com.apple.security.application-groups

Briefly: clear ~/Library/MobileDevice/Provisioning Profiles

If you are sure you have valid certificate and provisioning profile, then you may need to do the following:

I would suggest people to refresh the link between xCode and developer account by doing the following:

Go to Xcode -> Preferences -> Account -> View details -> (Refresh icon)

Otherwise you may not be able to see the provisioning profile as an option in the build settings (You may only see old profiles)

A lot of times it gives me connection error, you may need to retry.

Do this refresh every time you edit the provisioning profile or certificate online on apple developer member center

If certificates and build setting are all good, and you are part of multiple teams, make sure to select the proper team for the app. Clean and archive again.

I had another cause for this problem.

I had 3 different Configurations (Debug, AdHoc, AppStore). I accidentally had the AdHoc Configuration selected in the Archive Scheme setting and tried to upload the generated archive to the AppStore.

So setting the Archive configuration to AppStore solved the problem for me.

https://i.stack.imgur.com/6VKuX.png

It's the year 2017, and the provisions are still not just working. I had to put them on manual mode because automatic didn't worked after struggling half an hour. I have no idea what are those entitlements, i have no entitlements file.

After trying every possible fix in the world, I ended up just adding this to the entitlements file:

<key>beta-reports-active</key>
<true/>

Find the right entitlements file by looking in Targets > Build Settings > Code Signing > Code Signing Entitlements.

Maybe it's something to do with this Apple doc, although I couldn't follow the instructions fully as certain things were missing in XCode 7 (e.g. the refresh icon in Preferences > Accounts).

Another possible cause for this message is if you accidentally did remove the 'target inclusion checkbox' for the entitlement file – in that case the error message is slightly misleading...

In my case, the problem was caused by different Bundle Identifier in Target General tab than in Build Setttings.

If you have only development provisionning profile, just create distribution also

I played with fastlane gym, and there it gave some interesting insights:

There was an error exporting your application Unfortunately the new Xcode export API is unstable and causes problems on some project You can temporary use the :use_legacy_build_api option to get the build to work again

This is the according Bug-Report. Seems to be unfixed for month. https://openradar.appspot.com/radar?id=4952000420642816

Building the app in legacy mode worked for me.

gym --use_legacy_build_api true

Hope, this helps anyone.

In my entitlement file for Health kit there was development key. I removed that and my problem resolved.

I hope this answer could help :)

There seem to be many possible causes of this error.

In my case, my app was an Enterprise release and I was clicking "Validate" when I should have been heading straight to "Export".

I found this in the Apple docs:

Validate or Submit is not intended to be used with Development, Ad Hoc or Enterprise builds. Ad Hoc or Enterprise distributions should skip straight to Export.

Source: https://developer.apple.com/library/content/qa/qa1830/_index.html

I ran into this issue using App Groups. To resolve, I had to log into developer.apple.com and reassign the App Group ID to my App ID.

If other solutions do not work, try going to XCode -> Preferences -> Accounts -> View Details

Now look in Provisioning Profiles section. If your provisioning profile has an action button of 'Download', click the button and download. Then try again

Create a new provisioning profile

This solution worked for me when I had this problem.

Step by step :

https://i.stack.imgur.com/MZEGW.png

log onto the apple developer portal and go here : https://developer.apple.com/account/ios/profile/production Click the [+] add button and fill in a new profile name and select your app ID Click the Download button, and once it has downloaded double click to open that file in Xcode Re-Archive, and this time you should be able to upload succesfully to the store