Xcode 7. Application installation error: no valid provisioning profile found for this executable

Question

I have already searched and almost implemented the maximum solution, but it does not install any applications, even if I only create an example application with one view.

Application installation failed
No valid provisioning profile for this executable was found.

Answer 1

=============== update =====================

I fixed this question today. First go to ~/Library/MobileDevice/Provisioning Profiles . Make sure Xcode is not running. Then delete all initialization files (e.g. xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.mobileprovision).
Launch Xcode.
On the Main Generator tab, you will see something like "Fix this problem." Click on it. Xcode will now download the new provisioning profile.
What is it.

----------- OLD Answer -------------

I have the same problem now. I checked the preparation profile using https://github.com/chockenberry/Provisioning/releases .
In my case, my profiling had the wrong UDID, but the correct machine score.
I registered the machines, and the Apple Developer Center listed the correct UDIDs for these machines.
However, whenever I uploaded a new provisioning profile, it contained invalid UDIDs.
I think the Apple system displays the wrong provisioning profile.
Today I called Apple in support of this problem, but Apple just emailed me their links to knowledge bases (forums, documents, etc.).

Answer 2

Perhaps you are using the App Store distribution distribution profile. Use a development profile or ad-hoc.

Answer 3

For Xcode 8 / Swift 3.0 In my case, for my target application and my extension in "General" I check "Automatically manage signature" and it works

Answer 4

I had this problem because the date / time on my iPhone did not match the Xcode running on my Mac (I changed the date on my iPhone when testing some applications). On my iPhone, I went to Settings > General > Date & Time > Set Automatically

It fixed him

Answer 5

Make sure you add the device UDIDs to your provisioning profile.

• Go to the provisioning portal.
• Change training profile.
• Make sure the device is installed.
• Done download
• Use new profile

Another possible reason: the device date is set at a later date than the expiration of your profile. This is very strange, but it can happen.

Answer 6

In my case, it was that the launch parameter in the build scheme was set to Release, so he tried to sign it using the preliminary appstore profile, not development or adhoc. I had to install it in Debug to fix this!

Answer 7

I can work on Simulator just fine, but trying to install the application on the device threw this exact error.

I had a control goal in addition to the main goal. The target was signed with a different team and profile. Setting the unit test goal in accordance with the main target settings for signing a solution to my problem.

I did not notice that it was automatically changed to another team, caused by the fact that it was added to the new Enterprise team.

Answer 8

In my case, I went to the Apple Developer website and added the phone to the Provisioning Profile. Then I reloaded the Provisioning Profile and worked =)

Answer 9

For me, this is because the project that I tried to create is a stranger. The package ID does not match the training profile of my team.

Change the package id to something else.

Answer 10

In my case, my certificate is expired.

Answer 11

The following worked for me:

• Install the application using the personal security profile (reinstall it after entering the settings of your phone and trust the profile)
• Remove app from ypur phone
• Return to the registered developer profile and try again

Answer 12

In my case, there was a build system. I had to change the default build system in "File> Project / Workspace Settings" and change it to the Legacy Build system.