Alex Rivera | Logout

iPhone app signing: A valid signing identity matching this profile could not be found in your keychain

Asked 2009-06-16T02:10:04.803
317

I'm pulling my hair out over this. I just downloaded the iPhone 3.0 SDK, but now I can't get my provisioning profiles to work. Here is what I have tried:

  • Delete all provisioning profiles
  • Delete login keychain
  • Create new "login" keychain, make it default
  • Create a new certificate signing request
  • Create new developer and distribution certificates in the Apple developer center
  • Download and install them
  • Download the WWDR certificate and install it
  • Create a new provisioning profile and double click it to install

All the certificates report as valid, but Xcode still won't recognize them. What should I try next?

Edit:

I completely re-installed Mac OS X and from a fresh install installed the 3.0 SDK and still have the same problem.

ios xcode
Edit
Report

5 Answers

3

In my case, I copied the project from my iMac to my Macbook Pro and found out I didn't have my private key installed on the Macbook. So I exported my private key, copied and installed it to the Macbook, and voila it works! I've documented the information here: http://www.creatistblog.com/2009/09/iphone-developer-provisioning.html

answered 2009-09-22T02:04:20.050
2

There are two different certificates for two different provisioning profiles (development and distribution). You have to install BOTH certificates in keychain. In the iPhone Developer Program Portal:

Certificates -> Development -> Download Certificates -> Distribution -> Download

Double click both certificates. After that both certificates must appear in Keychain.

answered 2010-01-29T13:09:15.780
1

"This was a bug on the Apple portal site. They were missing a necessary field in the provisioning profile. They fixed this bug late on 6/16/09. "

answered 2009-06-17T18:03:10.937
1

I had the exact same problem and tried everything. For whatever reason the solution was that all my certificates had migrated to a keychain called "microsoft_intermediate_certificates". As it probably happened during an Xcode upgrade I have absolutely no idea why, but it may help somebody.

I moved all content of the Microsoft keychain to the login keychain and everything went back to normal.

answered 2009-06-27T17:25:59.560
1

I don't know whether they really skipped it or if my eyes were just glazing over but....

Just in case anybody else is overlooking the same things that I did....

just as when you were developing and testing...

1) You need a DISTRIBUTION << CERTIFICATE >> 2) You need a DISTRIBUTION << PROVISIONING PROFILE >>

That is TWO STEPS on the portal in order to get the thing signed.

There I was, having created the developer CERTIFICATE and copied it to the Mobile Provisions folder, wondering why it didn't work.

As soon as I had the provisioning profile in place

* BINGO *

answered 2011-05-23T07:20:52.403

Your Answer