Provisioning certificates

I am happy to now be the proud owner of an iPhone developer certificate from Apple, which will let me load and debug the iPhone applications I’m developing on my device itself.  I hadn’t actually planned to sign up to the developer program just yet, but I discovered something after my previous post:  VNC updates the screen too slowly for me to be able to play the game I’m developing full-speed!!  So without a spare monitor to plus into the Mini I’m left having to do most of my testing on-device.  Took a bit of stuffing around with the certificates, though.

When I first followed the instructions for provisioning Screen shot 2010-01-28 at 10.41.09 PMa device it all went fine.  Until I finished the instructions.  After completing the last instruction there was a very flagrant error on my screen: “A valid signing identity matching this profile could not be found in your keychain”. 

Turns out that the KeyChain has to have certificates for both the developer and the issuing authority for XCode to wanScreen shot 2010-01-28 at 10.45.45 PMt to play nice.  Without it I was prevented from selecting the certificate to use to sign my project, instead giving me the message:
“profile doesn’t match an valid certificate/private key pair in the default keychain”.

Turns out this is a pretty common issue for first-time developers, and some are still waiting for word back from Apple to help them with the issue!  The call for “delete all certificates and try again” was all over the forums, so I gave that a shot, with no success.

In the end, it turned out that when the original certificate had been signed, the Apple WWDC certifier certificate had ended up under my system keychain while the Developer certificate provided ended up in my user keychain.  A simple drag-and-drop of the Apple WWDC into the user keychain was all that was needed to get the show on the road.Before After

Leave a Reply

Your email address will not be published. Required fields are marked *