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.
Related
I got this mail from Apple.
Your iOS Distribution Certificate will no longer be valid in 30 days. To generate a new certificate, sign in and visit Certificates, Identifiers & Profiles.
I get some information from StackOverFlow but I want to know what I need to do if I modify my existing app. Will I able to update in future the same app with new certificate and new profile. Is that I need to revoke and generate the new certificate. Thanks for your help and comments.
As per new updates, you don't need to renew the certificate as a separate action. The renewal is based on the expiration of the Apple developer account. By taking the action of renewing your membership, this will automatically renew your certificates.
It is just a reminder of the certificate that is going to be expired very soon in future.
I want to know what I need to do if I modify my existing app. Will I able to update in future the same app with new certificate and new profile.
Yes, You can always able to create new certificates (Some has limitation to create) and use these certificate to generate new mobile provisioning profile or regenerate mobile provisioning profile using the new certificates.
Using old certificate (Expired) you can not able to run build on device and not able to publish app on App Store.
The new certificate will not affect on your app. In simple words, certificates are being used to run app on device, publish app on App Store, push notification, etc.
Last week we've transferred a published app in iTunes Connect to another company's account. Now they want us to provide an update to the app.
How do we sign, package and submit the app to them for publishing? Which Provisioning profile do we need to use? Do we still sign the .ipa with our team and send the .ipa to them or do we need to have additional info for this to work?
I hope someone is able to shed some light on this process, since the whole provisioning and signing process is hard to grasp for me.
Recently we have transferred our app to another company and we have pushed an update to the app. Let me explain you how we did
Once you transfer the app to another company account, you will not
be able to use your old certificates for publishing any new update
for app.
Apple by default removes your certificates and appid from your
previous account.
Apple generates an app id for your app in transferred account.
You can use this app id and create new certificate for your app and
publish the app by using new account.
You have to get the certificate and the private keys used to signe the application.
You import the private keys on your computer and install the certificate.
Then get the corresponding profile, compile, sign and post.
The other solution is to regenerate a new certificat with the keys on your computer, a new provisionning profile.
Then sign the app with those new files.
The certificate and profile need to be created from the new account.
My client has a few apps in the app store that were submitted using a certain App Store profile which I have access to the account. We also have those apps installed Ad Hoc signed with the same Distribution Profile. Now I am taking care of one of this apps and I need to code sign to make a few changes and then submit it Ad Hoc for some testers. No one knows where the .developerprofile backup is. Can I revoke the existing certificate and recreate a new one without affecting the apps on the App Store. If I revoke, any other developer using this key pair will stop working, right? Any other problem I am not remembering. Can I revoke the certificate?
Thanks in advance.
Yes, you can safely revoke the developer and AdHoc distribution certificates without affecting any App Store apps. Be careful not to revoke any Push Notification certificates if your app uses push.
Generate a new certificate signing request on your machine and use that to generate the new certificates. Remember to edit the provisioning profiles after you create the new certificates, especially if you've added any additional devices to the provisioning list. Then download the new provisioning profiles and you should be good to go.
Any other developers (if they still have access) will be able to download the new profiles if they need them. If they also need to sign builds, they should generate their own keys/certificates as well for their developer certificates.
I've developed and published an App on the App store successfully last month. However, since then, my Mac crashed and (stupidly!) I didn't have a backup of my Keychain Certificates. I've had to generate a new Certificate and ultimately create a new Developer Certificate in the Apple Provisioning Portal.
As a result - despite being able to sign and deploy the updated App to my iPhone and iPad, I cannot upload it to the App store because the signing is different.
Is there any way around this? Do I have to re-write the App and submit it a new with the new signing keys?
I've seen the question:
Can I upload a new version of my iOS app with a different certificate/profile than the previous one?
but this doesn't answer my question/problem.
your application bundle identifier & provisioning needs to be same which is irrespective with which distribution certificate you have compiled the build provided that you are generating build (ipa) for appstore submission from the same developer account.
Fixed! I logged into the Apple Provisioning Portal, revoked all my certificates and deleted all my distribution an provisioning certificates. Then I deleted everything from XCode and everything from my KeyChain. I re-generated a new CSR from the KeyChain, generates a new certificate in the Provisioning Portal with this and then did the rest through xCode. It found and downloaded my development and provisioning certificates, one against my team, the other as "unknown". I clicked on TEAMS in xCode and did a refresh then returning to the profiles say everything set as valid. I signed the App with the new certificates and uploaded them. The App is not awaiting review :)
I am currently fixing bugs for a client who had the iPhone app made by someone else.
I think i have to use the clients distribution certificate to upload the binary of update..
I downloaded the distribution certificate but Xcode is complaining valid sign identity not found.
I know it is an issue with the keychain .. i don't have accces to the keys of the original developer..
how to proceed?
Invalidate the certificate
Create a new one
Create a new distribution profile using the new certificate.
Install that profile in XCode
???
Profit :)
If use certificate from another person then you are in need of private key. Without private key, you will be unable to sign binaries in Xcode and test your application on any Apple device. Try to request a .p12 file from original developer for this certificate or create new one yourself.
Delete any certificates you might have from the provisioning portal
Create a new Certificate Signing Request on your mac
Upload that request to the Provisioning portal to generate a new certificate
Associate your existing provisioning profile to the newly generated Certificate
Add the new provisioning profile to XCode
Compile your app :-) Done.
This will not delete any app details. This is just creating a new certificate. You will still be able to use all your old details. So dont worry.