FCMv1 transition guide

Background

• Firebase will terminate the usage of Google Cloud Messaging (GCM)/Firebase Cloud Messaging (FCM) APIs on June 20, 2024.
• The existing users who have used Android mobile Push through GCM/FCM must migrate to FCMv1 APIs by 18:00 on June 19, 2024 (KST).
• The SENS service of NAVER Cloud Platform will provide the FCMv1 type functions from 20:00, March 7, 2024.

Transition Guide

How to switch

1. Register a certificate of FCMv1 type to the project you want to transfer. (Go to Firebase console)
2. Specify deviceType as fcmv1 in the Device token registration API, and then register tokens.
   • AS-IS: deviceType: GCM
   • TO-BE: deviceType: FCMv1
3. Send a message by specifying target.deviceType as FCMv1 in Send message API.
   • For target.deviceType: FCMv1, send a message to the user who has a device token registered as FCMv1 type
   • For target.deviceType: GCM, send a message to the user who has a device token registered as GCM type
   • For target.deviceType: ALL or if not specified, send a message to the user who has device tokens registered as all types (APNS, GCM, and FCMv1)
   • However, the function of sending to GCM will end after June 20, 2024.
4. You can use message.fcmv1 in Send message API.
   • If you configure and request message.fcmv1, you can separately control a message to a user who has a device token registered as FCMv1 type.
   • If you don't configure message.fcmv1 separately, the message sending to FCMv1 type will be used in the following order: message.gcm > message.default.

Precautions for transition

1. The SENS service of NAVER Cloud Platform will provide the functions related to the FCMv1 type after 20:00, March 7, 2024 (KST).
2. To use the functions of the FCMv1 type, register a certificate in advance.
3. If the same device token is registered as both GCM and FCMv1, target.deviceType: ALL, or without specifying it, duplicate messages may be sent.
4. No separate support is provided for device token migration from GCM to FCMv1, you can view device tokens registered as the existing GCM by using View device tokens API.
5. If you don't configure message.fcmv1 separately when sending a message, the message will be used in the following order: message.gcm > message.default. The section changed in FCMv1 can affect sending a message. Check 3. Changes in FCMv1.

FAQ

1. End date of support for functions of GCM/FCM type

• The functions will end at 18:00 on June 19, 2024 (KST).
• After that time, GCM/FCM certificates registered on the project will be deleted sequentially.

2. Start date of providing functions of FCMv1 type

• The functions will be provided at 20:00 on March 7, 2024 (KST).
• After that time, you must migrate to FCMv1 by 18:00, June 19, 2024 (KST) according to the above transition guide.

3. Changes in FCMv1

• The delay_while_idle option will be deleted.
• The name of the time_to_live option will be changed to ttl.
• The payload's data.KEY supported types will be changed.
  • Only the string:string format will be supported. See Firebase guide.
  • When you use the custom field in Send message API, you can only use string:string according to changing formats.
    • ex. custom.KEY(string) : VALUE(string)

4. How to download JSON files you want to upload to Private Key of FCMv1 type?

Go to Firebase console

1. Firebase project settings > cloud messaging tap
2. Click Manager service accounts on the Firebase Cloud Messaging API (V1) section
3. Create a service account for the project or select the existing account > click Manage keys
4. Add key > Create new key (select JSON as the Key type)