How do I resolve Firebase configuration errors with the Pushwoosh Unity SDK?

Configuration errors with Firebase Cloud Messaging (FCM) can prevent your app from registering for push notifications. These issues usually come from a mismatch between your Firebase project and either your Unity project or your Pushwoosh Android platform configuration.

Follow this checklist:

1. Verify google-services.json:

   • Download google-services.json from your Firebase project and place it in your Unity project's Assets folder.
   • Confirm that the package_name inside the file matches your Unity application's package name exactly.
   • The Firebase project is determined from this file. The legacy Pushwoosh.FcmProjectNumber (Sender ID) property is deprecated and is no longer required.

2. Check the Firebase project: In the Firebase Console, make sure an Android app has been added to the project and that its package name matches your Unity application's package name.

3. Check the Pushwoosh Android platform configuration: In the Pushwoosh Control Panel, open your project's Android platform settings and confirm that:

   • the Package name matches the one in Firebase and in your build, and
   • you have uploaded the FCM v1 service account JSON (Firebase Console → Project settings → Service accounts → Generate new private key) for the same Firebase project.

   The old FCM Server Key / Sender ID pair is no longer supported: Google discontinued legacy FCM server keys in June 2024, and Pushwoosh authenticates to FCM with the service-account JSON only. If your platform still shows a legacy configuration, re-upload the service account key.

4. Check dependency resolution: The Unity SDK requires the External Dependency Manager for Unity (EDM4U) to resolve the native Android dependencies. If it is missing, the Firebase/Pushwoosh Android libraries will not be pulled into the build.

See the Unity SDK basic integration guide for the current setup steps.