Why am I getting an error when adding or renewing my Safari push certificate?

First, check whether you still need a certificate. Safari on macOS Ventura (13) and later, and on iOS/iPadOS 16.4 and later, supports the standard VAPID web push protocol. Those browsers are covered by the All Browsers Configuration in Pushwoosh and need no Apple certificate, no Website Push ID and no .p12 file.

The separate Safari configuration with a .p12 certificate is only required if you want to keep supporting legacy Safari on macOS 10.14-12. If you do not need those versions, remove the Safari certificate configuration rather than renewing it.

If you do need the legacy Safari certificate

Errors during setup or renewal of a Safari push certificate are almost always caused by an inconsistent Website Push ID. The exact same ID (e.g. web.com.yourdomain) must be used in all four places:

1. Apple Developer account — the Website Push ID you created there.
2. The .p12 certificate — it must be generated for that specific Push ID.
3. Pushwoosh Control Panel — the Push ID entered in the project's Safari configuration.
4. Website initialization code — the safariWebsitePushID value in your Pushwoosh Web SDK init.

A mismatch in any one of these makes authentication fail. If you find a discrepancy, generate a new .p12 for the correct Push ID and update it both in Pushwoosh and in your site's init code.