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, which are required to send notifications, are permanently linked to the Firebase project that generated them. When you switch to a new Firebase project:

• Existing users will stop receiving push notifications. The push tokens from your old project will become invalid for the new configuration.
• To receive notifications again, users must update their app to a new version that is configured with your new Firebase project. When a user opens the updated app, a new token will be registered.
• Your push-enabled audience will recover gradually as users install the update.

Tip: You can use In-App Messages to communicate with users on older app versions and encourage them to update.

Steps to Change Your Firebase Project

Follow these two main steps to migrate to a new Firebase project:

1. Update and Release Your Application

   • In your Android app's source code, replace the old google-services.json file with the new one from your new Firebase project.
   • Build and release a new version of your app to the Google Play Store.

2. Update Your Pushwoosh Settings

   • In your Pushwoosh Control Panel, navigate to your application's settings and select the "Android" platform configuration.
   • In your new Firebase project's settings, go to the "Service Accounts" tab and generate a new private key (a JSON file).
   • Upload this new JSON file to the Firebase Private Key field in your Pushwoosh Android settings.
   • Ensure that the old "Server Key" and "Sender ID" fields are left empty.

Once these steps are completed, new users and users who update the app will be registered with the new Firebase project and will be able to receive push notifications.