CodeSign error: no provisioning profile found with UUID = '......'

I just had the same Problem. Here is how I fixed it:

Show the contents of your .xcodeproj project folder and open the .pbxproj file (Since this could potentially render the project file unusable, you should create a backup first!!!).

Now find all Lines that begin with +CODE SIGNIDENTITY = "+. In my case those lines contained values like

<pre>CODE SIGNIDENTITY = "iPhone Developer: x y"</pre>

I simply did remove the +iPhone Developer: x y+, making each occurence of that line read

<pre>CODE SIGNIDENTITY = ""</pre>

saved the changes, loaded the project in XCode and was able to build.

Make sure you do not alter the line +"CODE SIGNIDENTITY[sdk=iphoneos*]" = "+ as it contains the real value XCode is using.

I don't have a .pbxproj file for my iPhone App. I'm confused.

Go to the folder where your project file is stored (the *.xcodeproj file) ctrl-click on it and select "show package contents". A new Finder window willopen showing the contents of the package (including a *. pbxproj file).

Will it still build if you change the target SDK to a Simulator. In my case I was able to build for the device without a problem, but building for the Simulator (with the exact same settings) gave the CodeSign error.

Fwiw, i found that i also had PROVISIONING_PROFILE entries in my project file that i too had to remove, before tings started working again.

Make sure to clear the settings at the target level too. I always forget to do that.

thx u a lot!!

I got bitten by this today too. The problem seems to be that the same settings are used for everything, there's no difference between the simulator and the device settings, or at least I can't find a place to put them.

Now it appears, at least to me, that instead of having to set the iPhone Code Signing Identity field to "iPhone Developer:Roland King", and then pull my provisioning profile from the dropdown list, just leaving it at the default (iPhone Developer and Default .. etc ) works and it finds it, that's a change. It seems that if you actually go and set them, it tries to use the same settings for the simulator builds and that fails for .. I have no clue why.

I don't know what you're supposed to do if you have more than one provisioning profile as you couldn't leave it at default then.

I fixed this by the way without actually editing any files, I just clicked 'info' on the 'target' and went to the code signing section there and set everything back to default.

I think this doesn't really work quite right, the simulator builds should, I'm sure, ignore the code signing options and you should be able to set them for the phone builds to a specific code-signing profile.

All of the above experience has helped me "compile" my app which I have been unable to do because of the now famous "no provisioning profile" message. However, now that I can finally compile, I cannot deploy. When I try to deploy (run on the device) I get the message:

"Your mobile device has encountered an unexpected error (0xE800003A) during the install phase: verifying Application."

I have tried powering off the device and restarting my machine but nothing appears to help. Any suggestions?

This can be fixed by selecting the xcodeproj file while in xcode. With the "Build" tab selected, set the keypair "Default Provisioning Profile for Code Signing Identity" value for the Key

Code Signing Provisioning Profile

Code Signing Provisioning Profile, Any iPhone OS simulator

Thanks guys, I cleared out the line that said PROVISIONING_PROFILE and it worked out.

I was trying to compile and run one of Erica's examples from her new book, and load it onto the phone - I think my provisioning profile and settings she may have used when constructing her examples ending up not playing nicely together.