Closed vietdung97 closed 4 weeks ago
Hi @vietdung97,
This message comes up when trying to upload a file that has a different Sender ID than the current android subscribers are tied too.
You need to generate the Service Account JSON file from the same Firebase project as the current Sender ID found in the Cloud Messaging API (Legacy) > Sender ID
Details here as well. https://documentation.onesignal.com/docs/generate-firebase-credentials
@nan-li The Firebase project was set up by the legacy provider, I received an email saying we should update to FCM v1 because Legacy doesn't support the feature
Can you help me update it manually, I really need it because my app is available on Play Store. I can demonstrate anything if you want (except Firebase currently)
Hi @vietdung97, you should use the same Firebase project that is used for the Legacy FCM, and keep the same Sender ID after the migration. Otherwise, you will risk losing subscribers since they are tied to a different Sender ID.
If you need help finding your project, use the Sender ID saved under your legacy credentials to find the right Firebase project.
Do you no longer have access to your Legacy Firebase project?
You can reach out to support@onesignal.com with your OneSignal App ID and details of your issue, and the support team will help you.
Closing due to no response
How can we help?
My app required update FCM API (V1) so I tried setting up Google Android (FCM) but I got this error: You are attempting to add a Service Account JSON file with a new Sender ID. This will prevent current subscriptions from receiving notifications, as they are tied to the previous Sender ID. Ensure you are uploading the file associated with the previous Firebase Project that has the same Sender ID.
My app has:
Code of Conduct