GCM Mismatch Sender ID
969 views
Skip to first unread message
VJ Harish
Aug 14, 2019, 10:32:58 AM8/14/19
to Firebase Google Group
Concern / Issue:
We had one GCM project used in our application to send push notification to user devices. Because of GCM deprecation we migrated to FCM. But in course of migration we created a new FCM project(FCM1) without including existing GCM project and configured the google-services.json in client app. Also configured server key of FCM1 in server side and released it to end users.
Right now in production we have few users with older version of client app(configured with GCM sender ID) and device token generated by GCM. Also some users with FCM1 devcie tokens by updating the client app. Since these are two different projects, we are unable to send push notification to users who still have old GCM token by using FCM server key(throws "MismatchSenderId" error). This is expected, since the "Sender IDs" are different for these two projects.Below is the solution we are planning to implement:
To fix this issue we are planning to create a new FCM project(FCM2) by migrating the GCM project into it and send push notification to users(with GCM client app) using the new "Server Key". It is mentioned in https://developers.google.com/cloud-messaging/faq that GCM and FCM registration tokens are mutually interchangeable, we can send to existing GCM tokens through the FCM HTTP server APIs. Also to continue sending push notifications to FCM1 updated client app users using FCM1 "Server Key".
So the newly create FCM project(FCM2) is only to support push notification for users with GCM verison of client app. Once all the users updates the app to lastest version that has FCM1 configured in it, they will generate new FCM tokens which will be used to send push notifictaions in future using FCM1 "Server Key".According to the FCM standard / SDK:
Please confirm if this is the right way to send push notifications for users with old client app(GCM)? Or is there any other way we migrate the GCM project to the existing FCM project(FCM1) so that we can send push notifications to users with old client app(GCM) using FCM1 "Server Key"?
We had one GCM project used in our application to send push notification to user devices. Because of GCM deprecation we migrated to FCM. But in course of migration we created a new FCM project(FCM1) without including existing GCM project and configured the google-services.json in client app. Also configured server key of FCM1 in server side and released it to end users.
Right now in production we have few users with older version of client app(configured with GCM sender ID) and device token generated by GCM. Also some users with FCM1 devcie tokens by updating the client app. Since these are two different projects, we are unable to send push notification to users who still have old GCM token by using FCM server key(throws "MismatchSenderId" error). This is expected, since the "Sender IDs" are different for these two projects.Below is the solution we are planning to implement:
To fix this issue we are planning to create a new FCM project(FCM2) by migrating the GCM project into it and send push notification to users(with GCM client app) using the new "Server Key". It is mentioned in https://developers.google.com/cloud-messaging/faq that GCM and FCM registration tokens are mutually interchangeable, we can send to existing GCM tokens through the FCM HTTP server APIs. Also to continue sending push notifications to FCM1 updated client app users using FCM1 "Server Key".
So the newly create FCM project(FCM2) is only to support push notification for users with GCM verison of client app. Once all the users updates the app to lastest version that has FCM1 configured in it, they will generate new FCM tokens which will be used to send push notifictaions in future using FCM1 "Server Key".According to the FCM standard / SDK:
Please confirm if this is the right way to send push notifications for users with old client app(GCM)? Or is there any other way we migrate the GCM project to the existing FCM project(FCM1) so that we can send push notifications to users with old client app(GCM) using FCM1 "Server Key"?
Kato Richardson
Aug 14, 2019, 12:18:59 PM8/14/19
to Firebase Google Group
Hello VJ. There's no way for you to easily migrate registration tokens, so this looks like a workable solution.
☼, Kato
--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/703ff0b1-ef0f-41d4-a01e-73861a554303%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages