Web push in Pushwoosh is configured with a VAPID key pair, not with a Firebase credentials file. If you have lost access to the Firebase project, what actually matters is whether you can still retrieve the VAPID keys it held.
First: can you still recover the keys?
If anyone still has access to the Firebase console, open Project Settings > Cloud Messaging > Web Configuration, copy the key pair, and use the three-dot menu under Actions to Show private key. With both halves in hand you can keep your entire subscriber base:
- Go to Settings > Platform Configuration > Web Push Notifications and click Configure (or Reconfigure) under All browsers configuration.
- Select Use existing configuration.
- Paste the VAPID public key into Web Push Certificate and the private key into Web Push Private Key.
- Click Configure. Existing tokens stay valid and nobody has to resubscribe.
If the keys are unrecoverable
Then you must start a new configuration, and the existing tokens are lost — they are bound to the old key pair.
- Open the same screen and choose Create a new push configuration.
- Pushwoosh generates a fresh VAPID key pair and wires it into the SDK configuration automatically. You do not need Firebase at all for web push.
What happens to your subscribers
- Visitors who already granted the browser notification permission are resubscribed silently the next time they load a page with the Web SDK — no second permission prompt. Setting
autoSubscribe: truein your init parameters makes this happen without any user action. - Expect a spike of InvalidCredentials errors on the first sends after the switch: those are attempts against the old, now-invalid tokens. Pushwoosh removes those tokens automatically and the error count falls as visitors return.
- Users who never come back are not recoverable.
Caution: replacing VAPID keys affects your whole web push setup. Only do it when you genuinely cannot recover the existing pair.
Comments
0 comments
Please sign in to leave a comment.