We are recently started the migration from Certificate based approach push notification configuration to Token bases (APNS Keys) approach push notifications.
From Server side, its pretty straight forward that we need to use APNS Keys.
But We are facing one issue where we are not sure whether we can expire the existing push notification certificate that we are using so far or not.
If I expire the existing certificate, then it will also be removed from App Id configuration capabilities as shown below and when I create the provisioning profile for this Bundle Id, it doesn't contain the push notification capability and also shows error in the Xcode while using the profile.
can anyone help on this how to resolve this issue ? or any process or steps to follow for this migration ?
Thanks in advance.
Did you see the problem you are describing happen, or are you assuming it will happen.
The App ID configuration is not tied to having a push certificate. If you expire the certificate, the right hand side should now say Certificates(0) but the Push Notifications capability should still be enabled.
If it ends up being disabled, you can still enable it again, and create a new provisioning profile based on the new state of the App ID.
This will in no way effect the existing apps installed on user devices.
To make sure the token based authentication is working:
- have a saved App ID with Push notifications enabled
- have a provisioning profile for that App ID
- have built and run that app with the same Bundle ID once, and received a push token by calling
registerForRemoteNotifications()at least once
And of course tested that the push notifications are working by sending a test push.
As long as you are able to send a notification to the app by specifying the Bundle ID as the apns-topic in your token based push request, you will be good to go both for existing and newly built versions of the app.
Argun Tekant / DTS Engineer / Core Technologies
