Xcode 7: App installation failed: A valid provisioning profile for this executable was not found

Question

I have already searched and almost implemented max solution but it's not installing any app even though if I am creating just sample single view app.

App installation failed
A valid provisioning profile for this executable was not found.

There are a lot of possible duplicates. First of all your should look at your bundleId, then go to Code Sign Section and verify the bundleId of provision profiles you use to sign your app. If you logined to your developer account at Xcode - Preferences - Accounts, it can do automatically all the settings for you. — katleta3000, Oct 14 '15 at 13:40
I have checked those first, even tried other as well still facing same issue. — Sanoj Kashyap, Oct 14 '15 at 13:44
I had a watch target... the error finally went away once I re-created all my watch targets. — akiraspeirs, Oct 28 '15 at 01:00
You _might_ find it useful to read my blogpost @ Medium about [managing singing identity](https://medium.com/@euginedubinin/ios-tips-maintaining-your-signing-identities-and-certificates-c04c482ca493#.jtxicxgj7). — Yevhen Dubinin, Nov 19 '16 at 15:23

score 79 · Accepted Answer · edited Nov 15 '16 at 19:57

79

============== update ====================
I fixed this issue today.
First, go to ~/Library/MobileDevice/Provisioning Profiles. Make sure Xcode isn't running. Then, delete all provisioning files (like xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.mobileprovision).
Start Xcode.
You will see something like "Fix this issue" in your Target's General tab. Click it.
Xcode will now load new provisioning profile.
That's it.

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

I have same problem now.
I've checked my provisioning profile using https://github.com/chockenberry/Provisioning/releases.
In my case, my provisioning profile had the wrong UDIDs but right machine count.
I've registered machines, and Apple Developer Center listed right UDIDs for those machines.
However, whenever I downloaded new provisioning profile, it contained wrong UDIDs.
I think Apple's system is outputting wrong provisioning profile.
I called Apple support for this issue today, but Apple only emailed me with their knowledge base links(forums,documents,etc).

edited Nov 15 '16 at 19:57

rak appdev

717
8
21

answered Oct 15 '15 at 13:35

take

839
9
7

3

Thank you. This worked for me after upgrading from Xcode 6 to 7. – Anthony Oct 27 '15 at 23:20
1

Thank you! Worked for even, even when I only saw this message in the Device console of the destination device. – Leif Jan 11 '16 at 14:04
After restart, go to your account and download everything - then it worked for me! Brilliant! – David H Apr 20 '16 at 18:15
This is so great, thank you so much. In my case, I un-click my sigining "automatically manage signing" because I just transfer my app to other company account. – Wangdu Lin Feb 16 '17 at 03:50
Great. Thanks very much :D – Anik Islam Abhi May 15 '17 at 04:20
Didn't work for me. It is only one specific account from a customer that raises this issue – itinance Oct 02 '17 at 13:02
For others ending here with the same problem in Xcode 10+ read the answer below from Matías González – Martin Lyder Aug 07 '19 at 07:08

score 27 · Answer 2 · answered Jul 29 '16 at 10:01

27

Possibly you are using App Store distribution provisioning profile. Use development or Ad-Hoc provisioning profile.

answered Jul 29 '16 at 10:01

Avijit Nagare

8,482
7
39
68

score 17 · Answer 3 · answered Sep 16 '16 at 18:32

17

For Xcode 8 / Swift 3.0 In my case, for my app target and my extension in "General" I check "Automatically manage signing" and it work

answered Sep 16 '16 at 18:32

tolbard

1,273
15
20

score 11 · Answer 4 · answered Sep 14 '16 at 19:32

11

I was having this issue because the date/time on my iPhone was not the same as that on my Mac running Xcode ( i changed the date on my iPhone while testing some app). On my iPhone, i went to Settings > General > Date & Time > Set Automatically

This fixed it

answered Sep 14 '16 at 19:32

sga4

350
4
15

I spent almost 3 hours for this..... the error message Xcode is sending is very misleading. – J. Goce May 17 '17 at 08:36
Awesome!! I did not even think this is the scenario. I changed my date to future 2 years (for testing purpose). The date exceeds the date of certificate expiry date. – kalpa Dec 10 '18 at 09:06

score 8 · Answer 5 · answered Apr 03 '17 at 10:22

8

Make sure you have added device UDID in your provisioning profile.

Go to provisioning portal.
Edit provisioning profile.
Make sure device is checked.
Done, download
Use new Profile

Another possible reason: Device date is set to later than the expiry of you provisioning profile.This is very weird but, it could happen.

answered Apr 03 '17 at 10:22

Amit Tandel

883
7
16

In my case it was the reason. Thank you! – Marta Tenés Jul 04 '17 at 07:19

score 7 · Answer 6 · answered Aug 29 '16 at 11:55

7

In my case it was that the running option in the building scheme was set to Release so it was trying to sign it using the appstore provisional profile not the development or the adhoc one. I had to set it to Debug to fix this!

answered Aug 29 '16 at 11:55

XIII

2,036
16
25

1

This worked. In my case, I'm doing a unit testing and I have my own framework and it's building scheme was indeed set to Release instead of to Debug. Thanks! – Glenn Posadas Jun 14 '17 at 15:21

score 7 · Answer 7 · answered Feb 24 '17 at 07:37

7

I could run on Simulator just fine, but trying to install the App on device was throwing this exact error.

I had a test target in addition to the main target. The test target had signing set to a different team and profile. Setting the unit test target to match the main target settings for signing solved my issue.

Didn't notice it had been automatically changed over to a different team, was caused by being added to a new Enterprise team.

answered Feb 24 '17 at 07:37

DeadRat

89
1
1

Don't know why this was downvoted, it's a perfectly valid answer. (And one that I'm very happy to have found, as I had the exact same problem, so thanks.) – imre Jun 20 '17 at 18:06

score 1 · Answer 8 · answered Jan 20 '17 at 15:16

1

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

answered Jan 20 '17 at 15:16

Gabriel Guedes

73
8

score 1 · Answer 9 · answered Jun 12 '19 at 14:35

1

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

answered Jun 12 '19 at 14:35

Matías González

1,366
3
15
30

score 0 · Answer 10 · answered Nov 19 '16 at 15:18

0

For me, it's because the project I was trying to build is someone else's. The bundle identifier does not match with my team's provisioning profile.

Change bundle identifier to something else help.

answered Nov 19 '16 at 15:18

h--n

5,903
4
31
32

score 0 · Answer 11 · answered Feb 08 '17 at 08:57

0

In my case, my certificate is overdue..

answered Feb 08 '17 at 08:57

frank

2,327
1
18
20

score 0 · Answer 12 · answered Jun 29 '17 at 17:14

0

The following worked for me:

Install the app using Personal provision profile (re-install after going into your phone settings and trusting the profile)
Delete the app from ypur phone
Switch back to registered developer profile and try again

answered Jun 29 '17 at 17:14

Patrick Harrison

11
5

score 0 · Answer 13 · answered Feb 09 '21 at 11:59

0

In my case iOS 14.4, rebooting the iPhone solved it.

answered Feb 09 '21 at 11:59

7RedBits.com

454
6
6

Xcode 7: App installation failed: A valid provisioning profile for this executable was not found

13 Answers13

Linked