How do I change the Firebase project for my Android app and what are the consequences?

Changing the Firebase project linked to your application is a significant action with important consequences for your existing users.

Understanding the consequences

Push tokens are permanently tied to the Firebase project that generated them. When you switch to a new Firebase project:

• Existing users will stop receiving push notifications. Push tokens from the old project become invalid for the new configuration.
• To receive notifications again, users must update their app to a version configured with the new Firebase project. A new token is registered the first time they open the updated app.
• Your push-enabled audience recovers gradually as users install the update.

Tip: use In-App Messages to reach users still on older app versions and encourage them to update.

Steps to change your Firebase project

1. Update and release your application
   • Replace the old google-services.json in your Android source with the one from the new Firebase project.
   • Build and release a new version of the app to Google Play.
2. Update your Pushwoosh settings
   • In the new Firebase project, open Project settings → Service accounts and click Generate new private key to download the JSON key file.
   • In the Pushwoosh Control Panel go to Settings → Configure platforms, find the Android row and click Connect.
   • Use IMPORT FCM SERVICE ACCOUNT KEY to upload the new JSON key, then click Apply.

The FCM service account key is the only credential Pushwoosh uses for Android — the legacy Server Key and Sender ID were retired by Google in June 2024 and are no longer part of the platform configuration.

Once these steps are complete, new users and users who update the app will register against the new Firebase project and receive push notifications again.