Creating a new push certificate

Question:

We got a reminder from Pushwoosh that the Apple Push certificate we have on file is about to expire. What should we do?

Answer:

You do not need to rebuild or update your app - only the credentials stored in Pushwoosh have to be refreshed. There are two supported ways to configure the iOS platform:

Option 1 (recommended): token-based configuration (.p8 Auth Key)

An APNs Auth Key (.p8) does not expire, so you never have to renew it again. One key can be reused for all apps in your Apple Developer account.

• Create the key in the Apple Developer Portal (Keys section) and note the Key ID, Team ID and Bundle ID.
• In your Pushwoosh project go to Settings > Platform Configuration, click Configure in the iOS row and choose token-based configuration.
• Step-by-step guide: iOS token-based configuration.

Option 2: certificate-based configuration (.p12)

• Generate a certificate request in Keychain Access, create a new APNs certificate in the Apple Developer Portal, add it to Keychain and export it together with its private key as a .p12 file.
• Upload the .p12 with its private key password and select the Gateway in the iOS configuration form.
• Step-by-step guide: iOS certificate-based configuration.

Not sure which to pick? See Choosing between .p12 certificates and .p8 keys. Note that Live Activities require token-based configuration.

The legacy "Autoconfiguration" option is no longer available in the Control Panel.