I have some account with old certificate for an app that is currently in production. It's not duplicate of this question (Xcode apple developer certificate expiration: (0xE8008018)) because I know exactly what to do, but what harm it can does. Since I do not have CSR file that was used to create this certificate and app use a lot of push notifications.
Does revoking certificate will break push notifications?
What's about signing? If I revoke certificate I have to regenerate provisioning profile before pushing to store?
What will happen when I revoke certificate there?
You should review the Apple Support article on Certificates.
Does revoking certificate will break push notifications?
Yes, "you can no longer send push notifications to your app." At least not until you regenerate the cert and change your application to use the new one.
Distribution:
iOS Distribution Certificate (App Store)
If your Apple Developer Program membership is valid, your existing apps on the App Store will
not be affected. However, you will no longer be able to submit new
apps or updates to the App Store.
iOS Distribution Certificate (in-house, internal use apps)
Users will no longer be able to run apps that have been signed with this
certificate. You must distribute a new version of your app that is
signed with a new certificate.
Does revoking certificate will break push notifications?
Yes, if you revoke the certificate you will no longer receive push notifications to the app.
What's about signing? If I revoke certificate I have to regenerate provisioning profile before pushing to store?
If you create a new certificate and upload it to the server sending the push notifications you will be able to send push notifications again. This can be done without the need to build a new binary for the AppStore.
what harm it can does. Since I do not have CSR file that was used to create this certificate and app use a lot of push notifications.
Create a new certificate request and upload it to the correct app to create a new certificate in the developer portal. You do not need the original CSR file to do this.
In your case, Create a new certificate and replace the old cert on
push server with newly generated one. Cheers! All the pushes will
continue to deliver to users. But make sure do above thing just after
creation of new certificate.
Push cert is used for communication between your push server and APNS.
APNS allows push payload from the servers having valid certificates.
So replace the old cert with new one. I done it in past. No issue
faced. Push will be effected for the duration you would take to revoke
and update the certificates on push server.
Related
I have one app available on app store. It is more than 1 year old.
I am using Notifications so I have APNS production certificate.
All distribution certificates and provisioning profiles are expired now.
I want to release an update to the app. Will my notifications break if I release new version by new provisioning profile and distribution certificate?
Your notifications will not break if you upload new certificate.
Suggestion: instead of using APNS Certificate. You can use iOS APNS Auth Key which will be valid till your memebeship is active and moreover it can be used in all the apps which are released under same account. Here are the steps to generate Auth Key,
You need to update your expired apns certificate and update them on the server.
I need to revoke the APNS certificates as they are going to expire soon. I checked many answer but all questions are very old.
As when we create the APNS certificate then they need to add to key chain and then create the app for app store. So Are these certificates are used while creating ipa file.
My question is if I revoke and create APNS certificates the should i need to upload app to appstore again or should i just create new and change them on backend.
You don't have to recompile the app or resubmit the app to AppStore. Just create a new APNS certificate and test it with your current app. Once everything is fine, revoke the old certificate.
I have a question my distribution certificates are going to expire in 30 days. No as far as I know those apps which are on Appstore won't get affected by this but my client has more than 50 apps on App Store. Every app has push notifications as well so I have created them pem files as well. So after expiration do I have to create pem files again? I am concerned about Push Notifications, will they work even after this distribution certificate expires?
The push certificate cannot be renewed. You have to create a new one.
The push notification certificate is not part of the application build. Therefore for push to continue working you only have to create a new certificate and deploy the p12 file (or whatever other format you are using) at your server. You don't have to submit a new version of your app.
See this - Link
I am new to iOS develop this is first time for me to handle certificate which has been expired. After I renew certificate and replace it to server, I am not receiving push notification. I may did some mistake. Please correct me.
Below are the steps i followed:
step1-- Recreate push notification, production type is "Apple Push Services" I know apple do some change, but the development type still is "APNs ..."
If I can use new certificate for development and production environment why apple provide develop choice?
step2-- I also found the Ad Hoc certificate will expire, so I also recreate it, both development and production
step3-- Of course I recreate provisioning profiles, but when I create for development I can't distinguish which certificate is new one, so I revoked the old one.
step4-- Install new certificates and provisioning profile in my mac, then export p12 to server.
Then I can't receive push notification, someone said the new certificate need to update program to fix it, I hope after edit the code push notification will work fine.
But how about development push notification? the development certificate type is the same but I still can't receive push notification, or it caused by renew Ad Hoc certificate ?
========== edit at 3/3 ========
Because the new type of certificate can use for development and production at the same time, so after server side update its code, I test push notification with the new type of certificate both development and production, and this time I get push notification.
Maybe because I have new type of certificate so APNs doesn't accept old type of certificate, is it possible?
Go to Keychain Access, delete all expired certificates. Regenerate your push notification certificates from Developer Center along with new provisional profile.
I have transfered the app after I released new version push notification is not working
Thanks in advance
Even though the problem description is very lacking I think that the solution is very obvious: the APNS certificate is strongly linked to the Apple Member account certificates/provisioning files. If they don't match, the push won't come through.
That means, you have to sign your app with the same provisioning file (with the same bundle id) you've signed the old app with.
If you don't have the access to the old provisioning file's certificates, you have to create a new APNS certificate.
StackOverflow question explaining setting up APNS certs
or
certs tutorial
Either the original account owner has invalidated the original push notification certificate, or you have an error in your server unrelated to the transfer process.
I advice you to
Create a new push certificate.
Test that it works by sending a notification from a desktop app like APNS Pusher.
Update the push certificate in your server.