Titanium Community Questions & Answer Archive

We felt that 6+ years of knowledge should not die so this is the Titanium Community Questions & Answer Archive

iPhone Packaging Error: certificate/private key pair not found

Hey guys:

I recently upgraded to iOS SDK 4.0.2, as well as moving my project from Titanium mobile SDK 1.3 to 1.4. One of those changes has made it impossible to package my project for distribution. The build log says:

Code Sign error: The identity 'iPhone Distribution: null'
doesn't match any valid certificate/private key pair in the default keychain

I've revoked my old development certificate and created a new one, added it to my development provisioning profile, deleted my old certs and keys from Keychain Access and added the new ones (they're valid), and deleted and re-added the new provisioning profile to Titanium and XCode. I've also insured that my app id matches the app id in the provisioning profile.

I'm out of ideas… am I overlooking something simple?


— asked August 23rd 2010 by Scott Metoyer
  • distributing
  • iphone
  • mobile
  • provisioning

2 Answers

  • I'm pretty sure I answered my own question.

    I was able to create the distribution manually by opening the .xcodeproj in Xcode and changing the build target settings. I changed the Code Signing Identity from iPhone Distribution to iPhone Developer. I did not in fact have a distribution certificate installed on my development machine, which would explain the 'iPhone Distribution: null' error.

    What is strange is that it was working previously (using mobile sdk version 1.3)… was something changed in 1.4 that would make it impossible to create a distribution package using a development provisioning profile and certification?


    — answered August 24th 2010 by Scott Metoyer
  • I opened the .xcodeproj file but do not find a place to change the Code Signing Identity. It is not listed in Resources/Info.plist – would it be somewhere else?

    — answered June 9th 2011 by Eric Kinney
The ownership of individual contributions to this community generated content is retained by the authors of their contributions.
All trademarks remain the property of the respective owner.