Clever Geek Handbook

Another developer canceled and recreated my iOS distribution certificate for clients - does that mean I can never update an existing client app?

Here's the story:

  • A client hired us to make an iPhone app for them. This client has never made iPhone apps before and as part of this arrangement we have handled all aspects for them, including the presentation of the app store, and we handle a certain level of future development (new features, bug fixes / fixes, etc.).
  • We have created a distribution certificate and key pair for the client name
  • We have developed an application, published it in the App Store without incident
  • After a while, the client hired a second developer to make another application for them.
  • This second developer seems to have revoked the existing distribution certificate and created a new one with a new key pair on their system
  • This second developer shared a new distribution certificate and key pair with us for future reference.
  • Due to user error, this new certificate and key pair is now imported to the Macintosh where the original certificate and key pair for the original application we developed was generated and the originals were not copied.

So we have

  • # 1 App Store App with Distribution Certificate / Key Pair # 1
  • App # 2 is either in the App Store or will soon use distribution certificate / key pair # 2
  • Distribution certificate / key pair # 1 is now lost

So my question is, if we ever need to update app # 1, can we use using distribution certificate / key pair # 2? Or do we need to download it as a new app?

+3


source to share


1 answer


I think you're okay. As long as you have a valid key certificate and profile on the Mac from which you create the application, you can publish the new version. The package ID is what the application identifies. You just need a valid keyed certificate and a profile that matches. Make sure you are using the new signing credentials.



This same thing happened to me, except for the Enterprise application. After we got the new certificates and keys imported into the MBA, we could build and deploy fine.

+2


source






More articles:


All Articles