What should I do if my iOS Push Certificate for Pushwoosh has expired or is about to expire?

If your iOS Push Certificate (.p12 file) used for Pushwoosh has expired or is nearing expiration, your iOS users will stop receiving push notifications. To avoid disruption, update the credentials in your Pushwoosh project settings.

Here's how you can address this:

1. Recommended: switch to Token-Based Authentication (APNs Auth Key, .p8):

   • An APNs Auth Key (.p8) does not expire, so you never have to renew it again. One key also works for all of your apps in the same Apple Developer account.
   • You will need the .p8 key file, its Key ID, your Team ID and the app's Bundle ID from your Apple Developer account.
   • Follow iOS token-based configuration.

2. Or replace the expiring .p12 certificate:

   • Generate a new APNs certificate in your Apple Developer account and export it as a .p12 file.
   • Log in to the Pushwoosh Control Panel, go to Settings → Configure platforms for your project and open the iOS platform settings.
   • Upload the new .p12 certificate (and its password, if set), making sure the Gateway matches your build type (Sandbox for development builds, Production for TestFlight/App Store builds).
   • Step-by-step instructions: iOS certificate-based configuration.

Update the configuration before the old credentials expire so push delivery to your iOS users is not interrupted. If you have questions, consult the linked documentation or contact Pushwoosh support.