If your iOS push certificate has expired, your iOS users will stop receiving push notifications. This can happen even if you've recently updated it, as certificates have a defined validity period. To resolve this and ensure continuous service for your iOS app, you have two main options:
-
Renew and Re-upload Your Push Certificate:
- Generate a new push certificate (a
.p12
file) from your Apple Developer account. - Upload this new certificate to your application's iOS configuration section within the Pushwoosh control panel.
- For detailed steps, refer to our guide on iOS Platform Configuration.
- Important: Remember that push certificates expire. You will need to repeat this renewal process before the certificate's next expiration date to avoid service interruption.
- Generate a new push certificate (a
-
Switch to Token-Based Authentication (Recommended):
- This method uses an APNs authentication token (a
.p8
file) which does not expire. This eliminates the need for periodic certificate renewals and the risk of service interruption due to an overlooked expiration. - To switch, you'll need to obtain an APNs Auth Key from your Apple Developer account and upload it to your Pushwoosh application's iOS configuration.
- For detailed instructions, please see our guide on iOS Token-Based Configuration.
- This method uses an APNs authentication token (a
We strongly recommend switching to token-based authentication. It provides a more stable and long-term solution, preventing future disruptions caused by expired certificates and simplifying your push notification setup.
Comments
0 comments
Please sign in to leave a comment.