A Valid Provisioning Profile For This Executable Was Not Found

Sun, Oct 31

Over the past few months I’ve been working on a mobile commerce/payment project where my focus is on the architecture and design side of things, sans coding. This past weekend I started a development project and all was going swimmingly until I received the error message shown in the post title.

As far as I could recall nothing had changed since the last time I was in development mode: Xcode was cooperating, a development provisioning profile was installed and the application identifier was properly set in the build properties.

After walking away for a few hours, upon returning the lightblulb came on – I recalled that within the past few months I purchased a new iPhone 4. Yes, it should of been obvious that I needed to upload the new device UDID and generate a new development provisioning profile, however, I’d been using the same device for quite some time and it was second nature to simply plug in my phone and install an app.

Although the message above is correct in that the provisioning profile was not valid, I may not of been sidetracked if there was a litt more detail provided, specifically: “A valid provisioning profile for this device was not found.” The takeaway for me with this (and most all error messages) is to read between the lines – at the highest level the information was correct, I just needed to think one level deeper to get to the crux of the problem.

I realize this post will apply to only a select few who run into a similar issue, yet hopefully it will save someone a few hours of debugging.

2 comments

Sadly, this can apparently happen even when nothing has changed except for the installation of a new OS on the device. They still have some work to do on the whole provisioning process.

by Michelle on Nov 2, 2010. #

I often met such issues.

there are different reasons, but best way I got now is to clean all, and went through the whole procedure several minutes, then you will understand all.

for your case, I guess that you should use your private key to sign your cert.

by Forrest on Nov 21, 2010. #