I have an app at the appstore.
Now I want to switch developers.
If the old developer won't give me the private key for the distribution certificate, what are my options?
If I revoke my existing distribution certificate and create a new one, I understand that my existing app in the store cannot be updated.
On the other hand, if I wait until my current distribution certificate expires, then create a new one, then my app at the store should be updatable?
Please whoever can clarify this issue will be blessed!
You will be fine with revoking your distribution certificate and making a new one. You can still update an existing app after doing this.
Relevant info:
Lost Private Key For iPhone Distribution Certificate. What could be solutions?
If I revoke an existing distribution certificate, will it mess up anything with existing apps?
Related
While I try to create the iOS distribution certificate it says your account reached the maximum limit for distribution. if revoked one of the iOS distribution certificates. Is that cause any problem on the app that I have already the push to the app store with this certificate?
Well we can create 2 distribution certificates from a single account, revoking one will NOT CAUSE any harm to launch apps on app store. YOU CAN CREATE ONE AFTER REVOKING ONE FOR yourself and edit the provisional profile also with new certificate that you created.
the only consequence is no one will able to launch the app from the revoked one he has to get the new one along with he has to renew his provisional certi also
Your App distribution uses exportMethod as Ad-Hoc, (e.g. Firebase Distribution), will no able to launch and install.
My terrible experience.
I have a live app on App Store, but found that the distribution certificate for it has been revoked by someone and we don't know who is it.
Is it possible to generate new distribution certificate for it without affecting currently live app on App Store? Or is it better to revoke and re-generate?
You can revoke a Distribution certificate without affecting apps in the App Store. Once it's revoked you can generate a new one that can be used to sign a new build for submission.
You have it right — revoke the distribution certificate then re-create it.
Generally you would follow this protocol when:
1. You no longer need them.
2. There's code signing issues.
3. You suspect that they have been compromised.
4. Team members no longer work on your project.
Revoking development or distribution certificates doesn’t affect apps that you’ve submitted to the store nor does it affect your
ability to update them.
The entire procedure is explained in more detail here:
↳ Maintaining Your Signing Identities and Certificates: Revoking Certificates
I have a doubt on Code Signing during Appstore submission. I already submitted an app to appstore with the profiles and certs created and its currrently in appstore. Unfortunately, i lost my machine where i had backup of those profiles and certs. I know that Prov Profile can be downloaded from my developer account.
My Doubt here is, 1) As i dont have backup of .p12, should i need to raise a request for new certificate from my keychain and proceed with that?
2) If so, will users can be able to upgrade the existing app from the appstore?
Thanks in Advance.
Here are your answers
1) As I don't have backup of certificate and .p12, should I need to raise a request for new certificate from my keychain and proceed with that?
Don't worry, when you like to give new update for your application, create new .p12 file and use it. Certificates are used to basically authenticate your machine with developer account.
2) If so, will users can be able to upgrade the existing app from the appstore?
No problem for users, as app store distribution provisioning profile works very different from developer provisioning profile, so no user needs to update.
Just for your info: the signing files for Android are very important, not for iPhone application. For Android, if signing keys are lost, you cannot update apps, whereas for iPhone you can create new certificates and update your apps.
Yes, you can just request a new production certificate from your new machine.
Then use it for your old provisioning profile for the app.
Yes without private key in your keychain, You cant use the existing provision files created with that private key. So you need to create a new Developer/Distribution certificates in developer portal with new Certificates. This will not affect the existing application in appstore.
Tried reading around but there's a lot of information around which negates itself
I have an app which I built with a certain distribution certificate, those certificate's private keys are lost to me now...
I want to create a new distribution certificate, and a new provisioning profile without revoking the old one... because the old needs to remain active on the places I've installed it on... I can't afford to re-publish it.
will uploading a new certificate ruin the old certificate?
I should mention I am using an enterprise account to distribute the app.
do I have ANY other choice other than revoking and re-install my app on all devices for my account?
Uploading the new certificate to the Apple dev a/c and creating the new profile will not ruin the old certificate. As long as the old certificate is valid, application with that certificate will continue to work.
I want to create provision certificate for development and testing purpose.
I login Apple web site and going to https://developer.apple.com/ios
But I did one mistake during certificate creation i revoking distribution profile... Now I am worried if I revoke distribution profile then the distribution binary on app store is not working if during this time any body download my application from app store? How do I go back if I revoke the distribution certificate?
If in not able to go back on real certificate then what is will be the solution of it?
Don't worry, if you revoke the distribution certificate or profile, it only means that you can't create a new binary for Ad-Hoc or App Store until you create a new one. No problems, don't panic.
Oh and you can't "go back", once it's gone - it's gone, just create a new one.