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 services has expired or is nearing its expiration date, your iOS users may stop receiving push notifications. To prevent any disruption in service, you need to update your certificate in your Pushwoosh application settings.

Here’s how you can address this:

1. Update your iOS Push Certificate (.p12 file):

   • You will need to generate a new .p12 certificate from your Apple Developer account.
   • Once you have the new certificate, log in to your Pushwoosh account and navigate to your application's configuration page.
   • Upload the new .p12 certificate to your Pushwoosh application's iOS platform settings.
   • For detailed, step-by-step instructions, please refer to the Pushwoosh documentation on iOS Platform Configuration.

2. Alternatively, consider switching to Token-Based Authentication (Auth Key .p8 file):

   • Pushwoosh also supports token-based authentication for the Apple Push Notification service (APNs). A significant advantage of this method is that it does not require periodic certificate renewals, which can simplify your setup and long-term maintenance.
   • To learn how to switch to token-based authentication using an .p8 auth key, please follow the guide on iOS Token-Based Configuration.

It is crucial to update your configuration promptly to ensure uninterrupted push notification delivery to your iOS users. If you have any questions or need assistance during this process, please consult the linked Pushwoosh documentation.