A valid provisioning profile for this executable was not found again

Question

I know this has been asked and answered multiple times but I m tearing my hair out as none of the proposed solutions appears to work     I receive the above error  despite having a valid provisioning profile which  as far as I can tell matches the bundle identifier     I ve followed the steps in various suggested solutions on this site  including deleting all existing certificates and starting again  as suggested here and here   One thing I have noticed is that the profile doesn t show up in the code signing lists  either for target or project   Can anyone offer any further suggestions

User · Answer

1 to banging my head against the wall for a day or two     Also check this setting      Build Settings -  Code Signing -  Provisioning Profile   After following the above steps   Automatic  setting worked for me   kjm

User · Answer

Make sure you have added your device - https   developer apple com account ios device create  Go into iTunes and click on the serial number and it ll change to the UDID - then right click to Copy the UDID and register it as your device   You can then add that device to your provisioning profile

User · Answer

After wasting my half day I got this working   Select Target  gt  Edit Scheme  gt  Select Run  gt  Change Build Configuration to debug

User · Answer

In my case  it was the problem when I setup my time manually two month earlier on my iPhone  But when I changed to set time automatically  it worked fine   Setting -  General -  Date  amp  Time -  set time automatically  If it does not work then set time automatically of both mac  amp  iPhone  it may work fine

User · Answer

This can happen if your provisioning profile has expired  Another reason could be that you device date exceeds the expiry date of your provisioning profile  Please make sure that your device date is correct

User · Answer

This happened to me yesterday   What happened was that when I added the device Xcode included it in the wrong profile by default   This is easier to fix now that Apple has updated the provisioning portal    Log in to developer apple com ios and click Certificates  Identifiers  amp  Profiles Click devices and make sure that the device in question is listed Click provisioning profiles   All and select the one you want to use Click the edit button You will see another devices list which also has a label which will probably say  3 of 4 devices selected  or something of that nature  Check the select all box or scroll through the list and check the device   If your device was unchecked  this is your problem  Click  Generate  DON T hit Download  amp  Install     while this will work it s likely to screw up your project file if you ve already installed the provisioning profile  see this question for more info   Open Xcode  open the Organizer  switch to the Devices tab  and hit the Refresh button in the lower right corner   This will pull in the changes to the provisioning profile    Now it should work

User · Answer

I m still not sure what the issue was but deleting all certificates and starting over  albeit twice  eventually solved it    My best guess is that I ve missed some small but important detail of the procedure  Unfortunately I can t be any more specific than that

User · Answer

I had this error because I was testing my app to perform a certain action in the future  In other words  I had a different time on my test device  therefore  the certificate would not allow me to build    Apparently  my certificate expires in a few days

User · Answer

In my case it was just after a new Program Licence Agreement was released so we had to accept them and it was fine

User · Answer

Delete all certificates from the keychain of the account which you are trying to use provisioning profile Delete Derived data  Clean the folder cmd sht alt k  Clean the project cmd sht k  Build  amp  Run

User · Answer

File  gt  Workspace Settings  gt  Set Build system to  Legacy Build System

User · Answer

If none of above stated works then check for your device date  make sure your device date doesn t exceed profile expiry date i e  not set to far future

User · Answer

Xcode5 has broken this again  congratulations to Apple for failing to bother testing one of their buggiest bits of code  Again    A new way to break fix it   If you have    An old profile on your device  team profile  or non-team profile  A new profile generated automatically on the App Store  by any copy of Xcode5  even if it s simply an update to the profile you already had  NB  if any colleague adds themself to the profile  this triggers the above  change   You use the new  Accounts  dialog to download profiles  NB  this is now REQUIRED by Apple for various situations - all other approaches  including manual download  appear to be unsupported  Even though the Apple Developer site TELLS YOU TO MANUALLY DOWNLOAD  Don t do it  It breaks Xcode5   Xcode5 will INCORRECTLY hide AND RENAME that profile in the drop-down selector in Build Settings  I detest this drop-down  Some idiot at Apple keeps removing information from it  and someone else keeps adding it back  it flip-flops between Xcode point releases  WHY       There is NO WAY you can select the correct profile - whatever you select  Xcode5 will use the wrong one   The solution is easy enough  The  Apple engineering are lazy  solution    Go to Xcode5 -  Window -  Organizer -  Devices Select your device Select provisioning profiles Delete everything relating to your current project and or Team  even other projects  if necessary - they can all be downloaded later if still needed   Re-build  You should get an error from Xcode5 that the profile doesn t exist  Even though you manually had seleted the profile that was ALREADY PRESENT on your machine  yep - that dropdown is buggy again  It lies about the profile it selects behind the scenes   In the profile selector  select the  real  profile Build  run - success

User · Answer

I have spent about a week solving this problem  Most of the answers are sort of magic  no logical purposes for these algorithms  and they were not useful for me  I found this error in Xcode console   ERROR ITMS-90174   Missing Provisioning Profile - iOS Apps must contain a provisioning profile in a file named embedded mobileprovision     And found this answer solving this issue  The case is to switch Xcode Build system to the Legacy one   I was deploying my Ionic app

User · Answer

After spending the day I realized it was a simple change in Project Settings  File -  Project Settings    -  Build System -  Legacy Build System   In a project setting  you will see Build System named drop down and in that drop down select Legacy Build System

User · Answer

It happened to me when I accidentally left the build in release mode

[xcode] A valid provisioning profile for this executable was not found... (again)

Examples related to xcode

Examples related to certificate

Examples related to provisioning-profile