Short version:
Is it necessary or even possible for me to generate a new distribution certificate based on my existing private key, or is there no harm, both for new applications and for updating existing applications in the application store, to create a new certificate with a new private key?
Long version:
It seems to me that the user guide for the iPhone developer program has conflicting / misleading information about private keys and the expiration of the distribution certificate.
On the one hand, it says that you must protect your secret key with your life and keep a copy of it so that you can use it on a new machine if you change developer machines. My understanding was that somehow you have to stick to your only private key (i.e. the first one that you create for your company when you request your first certificate) and use it forever (at least use it forever after you deployed the app with it in the App Store).
On the other hand, it informs you that the distribution certificates expire in a year, and you can simply request a new distribution certificate when you need it. What would be reasonable for me would be if they followed this with the paragraph that began, “Since it is important for you to use your original private key when requesting a new certificate, this is how you request a certificate created from pre-code, an existing private key ... "But there is no such paragraph, and after searching I have not heard about how to do this.
This is closely related mail in stackoverflow: The Lost Secret Key for the iPhone Distribution Certificate. What could be the solution?
, , , , , , , , Apple : ", , ".
, , , /, , . , .
, : Apple, , - , ? itunesconnect, ?