Xcode6 Error: "There are no suitable provisioning profiles for the application"

Question

I am trying to send an iOS application in Xcode6. When I click "Submit" or "Check" in the organizer, a window appears that says:

Could not find or create matching signature assets:

Xcode tried to find or create matching signature assets and was unable to do this due to the following problems:

No matching training profiles found for "Applications / MyApp.app"

None of the valid training profiles allowed the specified access rights: application identifier, active beta reports, keychain for group access keys.

I created a distribution provisioning profile for this application in the member center and appears in Xcode. I looked around and found nothing on the Internet that told me how to fix it. Can anyone help? Thank.

Andy

Answer 1

There are several possibilities for your problem, but the main reasons are what I got from experience, as well as other SO answers.

• Your certificate or profile is out of date, in which case you need to update your profiles again and again. I used to have this problem, but Apple described (partially) this problem.

• You have not set your profile in the Build Settings/Code Signing with the corresponding certificates. Confirm your Team in General/Identity and make sure your profile is installed correctly.

  From Xcode 5: Error signing code (image is a bit outdated, but it's the same as Xcode 6):

• You are using the beta version of Xcode.
• @jaytrixz reads: "I just deleted Entitlements.plist with code signing rights in the build settings" that might work. Make sure the configuration profiles are configured as well.

Answer 2

Like jaytrixz wrote in the comments ...

"I just deleted Entitlements.plist as code signing rights in the build settings"

I did the same, and he worked an hour later, trying to try other things!

Answer 3

There are many answers here, some of them have worked for me in the past, but not this time. I even created a new training profile, but it still didn't help. Based on the “None of the valid training profiles allowed specific rights” part of the error, I tried the following for hunch, and this worked for me:

1. add and remove a specific feature

Go to Goals> Features and turn it on, then turn it off.
I doubt that you chose, I added "Push Notifications" (which I do not need for my application), when it was "ON", I changed it to "OFF"

2. Archive again

Now I successfully upload my application to the store.

Answer 4

Another solution that fixed this symptom for me can be found at: Xcode Watchkit: none of the valid training profiles allowed the specified rights: beta-reports-active, com. apple.security.application group

Briefly: clear ~/Library/MobileDevice/Provisioning Profiles

Answer 5

If you are sure that you have a valid certificate and training profile, you may need to do the following:

I would suggest people update the connection between xCode and the developer account by doing the following:

Go to Xcode → Settings → Account → Details → (refresh icon)

Otherwise, you will not be able to see the preparation profile as an option in the build settings (you can only see old profiles)

Many times this gives me a connection error, you may need to try again.

Make this update every time you edit a training profile or certificate online at the Apple Developer Center.

Answer 6

If the certificates and build settings are good, and you are part of several teams, make sure to select the appropriate command for the application . Clean and archive again.

Answer 7

I had another reason for this problem.

I had 3 different configurations (Debug, AdHoc, AppStore) . I accidentally chose the AdHoc configuration in the settings of the archive scheme and tried to load the generated archive into the AppStore.

Therefore, configuring the archive configuration in the AppStore solved the problem for me.

Answer 8

This is 2017, and regulations are still not just working. I had to put them in manual mode because the automatic work did not work after it worked for an hour and a half. I have no idea what these rights are; I don't have a rights file.

Answer 9

After using all the possible fixes in the world , I just added this to the rights file:

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

Find the correct permissions file by looking at Targets > Build Settings > Code Signing > Code Signing Entitlements .

There might be something related to this Apple document , although I couldn’t fully follow the instructions because some things were missing in Xcode 7 (for example, the update icon in Settings> Accounts).

Answer 10

Another possible reason for this message is that you accidentally deleted the “target inclusion” check box for the right file - in this case, the error message is a little misleading ...

Answer 11

In my case, the problem was caused by different Bundle Identifiers on the General Goals tab than in Set Settings.

Answer 12

If you only have a development support profile, just create a distribution and

Answer 13

I played in the Fastlane gym, and there he gave interesting impressions:

An error occurred while exporting the application. Unfortunately, the Xcode export API is unstable and causes problems in some projects. can temporarily use the parameter: use_legacy_build_api to get the assembly work again

This is an appropriate error report. It seems that he is not attached to the month. https://openradar.appspot.com/radar?id=4952000420642816

Building the application in obsolete mode worked for me.

 gym --use_legacy_build_api true 

Hope this helps anyone.

Answer 14

There was a development key in my health set rights file. I deleted it and my problem was resolved.

I hope this answer can help :)

Answer 15

There seem to be many possible causes for this error.

In my case, my application was an Enterprise release, and I clicked Validate when I needed to go directly to Export .

I found this in Apple docs:

Verify or Submit is not intended for use with development, Ad Hoc, or Enterprise builds. Special or corporate distributions should pass directly to Export.

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

Answer 16

I ran into this problem using application groups. To solve the problem, I had to go into developer.apple.com and reassign the application group id to my application id.

Answer 17

If other solutions do not work, try switching to Xcode → Settings → Accounts → View details

Now review the Profiling section. If your provisioning profile has an “Download” action button, click the button and download. Then try again

Answer 18

Create a new training profile

This solution worked for me when I had this problem.

Step by step:

• go to the Apple developer portal and go here: https://developer.apple.com/account/ios/profile/production

• Click the [+] add button and enter a new profile name and select your application identifier

• Click the Download button, and once it has double-clicked to open this file in Xcode

• Re-Archive, and this time you can successfully upload to the store