I'm trying to distribute a new version of the app (it can be installed OTA) and I got the error:
"Code Sign error: No matching provisioning profile found: Your build settings specify a provisioning profile with the UUID “AdHocProfile”, however, no such provisioning profile was found. " and Xcode gets stuck in the process of automatically fix the error:
I have spent a lot of hours in the weekend looking for a solution here and on the internet, only to get rid of one of the two errors I got when I tried to archive the app to distribute it "Ad Hoc".
I made some capture screens to clarify what I've done:
Provisioning profile at Developer site:
My account: certificates and profiles:
Project Settings:
Target Settings (Xcode changed them when I deleted the line PROVISIONING_PROFILE in project.pbxproj):
I deleted the line containing PROVISIONING_PROFILE in project.pbxproj, following the directions found in posts similar to this
I also removed both the stable and the beta versions of Xcode and reinstalled it from the App Store. Don't know if it's important, but I removed the beta 5.1.3 with App Cleaner, deleting all the files associated to it.
Since Xcode does not longer show the values on the popup to choose certificates, I am not sure if I choose the correct ones.
Could you please help me to solve this issue?
This took me a long time to figure out. I wasn't keen to redo all my profiles and certificates like some of the people suggested. My error message was saying ""Code Sign error: No matching provisioning profile found: Your build settings specify a provisioning profile with the UUID “6278e001-8887-4fe4-a95c-a722c896792f”" but then when I went into ~/Library/MobileDevice/Provisioning\ Profiles
and printed out all the files using ls -la
I could clearly see the profile there.
I tried doing a Clean
and Clean Build Folder...
. I then tried to remove derived data. None of this worked.
But then when I simply quit Xcode and opened it again it worked
Xcode must be storing a cache somewhere when it opens up. This seems crazy to me. But what can we do.
I hope this helps someone.