Why do I see a warning to re-configure Chrome/Firefox by uploading a Firebase JSON file?

You may still see a legacy warning in the Control Panel asking you to re-configure Chrome and Firefox by uploading a private key .json file from the Firebase Console. That message refers to a retired configuration method and you can safely ignore it if your web pushes are being delivered.

How web push is configured today

Chrome and Firefox are no longer configured as separate platforms. Web push is a single platform based on VAPID keys:

1. Go to Settings → Platform Configuration → Web Push Notifications and click Configure.
2. Under All browsers configuration (this covers every modern browser, including current Safari), click Configure and choose one of:
   • Create a new push configuration — Pushwoosh generates a new VAPID key pair for you. Use this if you have not run web push through another service before.
   • Use existing configuration — paste VAPID keys you already own (for example from Firebase) so your existing subscribers do not have to opt in again.
3. Older Safari versions (macOS 10.14–12) are the only case that still needs a separate setup, using credentials from Apple.

No Firebase service-account or private-key .json file is uploaded at any point in this flow.

How to confirm you are fine

Open Settings → Platform Configuration → Web Push Notifications and check that a configuration is present, then send a test push to a test browser. If it arrives, the warning is cosmetic. If it does not, re-run the configuration above rather than looking for a Firebase JSON file.

See Web push configuration.