What happens to older clients when you migrate an

问题:

I'm considering migration to FCM. The client side of things is rather simple, you move some code around and get it done. However, on the app server, I'd need to support older clients as well, for obvious reasons. I need to know what happens when I migrate a GCM project to FCM. Does FCM automatically forward messages to older GCM-based clients as well? Or would I need to send each message twice, once to FCM and once to GCM? How will this impact implementation-specific stuff such as messages sent from Firebase's web console? Are there any details I should be aware of?

回答1:

Using FCM (an imported project or using it's endpoint, whichever you mean) is still compatible with GCM clients (specifically tokens). They'd still be able to receive messages like usual.

See these similar posts:

• https://stackoverflow.com/a/37517339/4625829
• https://stackoverflow.com/a/42674121/4625829

回答2:

FCM act as platform for triggering notification and internally GCM control notification whether you use FCM,Localytics ,mixpanel etc as you platform. As long as Api key is same for any paltform.You don't have to worry about FCM or GCM.

Just make sure you are using same server key (Api Key) for FCM which was for GCM.

Alternatively Check below link for details for FCM solution to handle such case .

https://support.pushcrew.com/support/solutions/articles/9000064351-setting-up-your-fcm-keys-previously-called-gcm-

回答3:

Either you might need to send notification manually to both versions of client as GCM and FCM are not exactly same.

Better way is to enable force upgrade (If implemented in app) so that all user base can move to new version of app.