{"_id":"5c4076388ab471005d3d7951","project":"54aa7f773b56130b0056c86e","version":{"_id":"55781fe25129590d003ff4f7","project":"54aa7f773b56130b0056c86e","forked_from":"54aa7f773b56130b0056c871","__v":8,"createdAt":"2015-06-10T11:30:42.700Z","releaseDate":"2015-06-10T11:30:42.700Z","categories":["55781fe35129590d003ff4f8","55781fe35129590d003ff4f9","55781fe35129590d003ff4fa","55781fe35129590d003ff4fb","55781fe35129590d003ff4fc","55781fe35129590d003ff4fd","55781fe35129590d003ff4fe","564bbc7e8841060d00abb2ee","565b66c446118c0d00dcb0bb","56898269f8dc340d00308c13","582318b23b961a0f009516a1","594a848c9f4771001a43c959","5c73dd27e8fdc000572a206a","5c77ac5af94a920045cb80ca"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"Developers","version_clean":"2.0.0","version":"2.0"},"category":{"_id":"55781fe35129590d003ff4fc","pages":["55781fe45129590d003ff50d","55781fe45129590d003ff50e","55781fe45129590d003ff50f","55781fe45129590d003ff510","55781fe45129590d003ff511","55781fe45129590d003ff512","55781fe45129590d003ff513","55781fe45129590d003ff514","55781fe45129590d003ff515","55781fe45129590d003ff516","55f692b4fe4cce21005c78b0","55f7e91e60cc850d008a7a45","56333cab9c607719001b85e4","564462ed9ce94c0d00068ce9","564f54fa48a1df1700836653","565ee9e7413e06170093dde0","5661a8fdb401c70d00dde6fa","5671348860c8e70d006c96a1","568ce9707d3bf02300aa7734"],"version":"55781fe25129590d003ff4f7","__v":10,"project":"54aa7f773b56130b0056c86e","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-01-05T12:44:00.338Z","from_sync":false,"order":4,"slug":"android-sdk","title":"Android SDK"},"user":"577cf7765fd4de0e00cc3d50","__v":0,"parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2019-01-17T12:34:00.179Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":6,"body":"[block:callout]\n{\n  \"type\": \"success\",\n  \"body\": \"Any apps that are integrating Pulsate for the first time should use our guide [here](https://pulsate.readme.io/docs/fcm-configuration) for configuring push notifications using Firebase Cloud Messaging (FCM)\"\n}\n[/block]\nOn the 11th of April, 2019, Google will be deprecating their Google Cloud Messaging service and anyone who wishes to send push notifications to Android devices will need to use Firebase Cloud Messaging (FCM). \n\nPulsate has used GCM to deliver push notifications on Android up until this point and we will now be migrating over to support FCM instead. This will require all Pulsate clients who have an Android app to migrate to FCM as well. Google have provided a guide to migrate from FCM to GCM [here.](https://developers.google.com/cloud-messaging/android/android-migrate-fcm)\n\nPulsate will be removing direct support for GCM on March 1st ahead of Google deprecating the GCM service on April 11th. Currently, FCM and GCM tokens are interchangeable and can be used to send pushes on either service. However, this is likely to change on April 11th so every developer will need to update their implementation to use FCM instead of GCM.\n\nTo ensure the migration process is as straightforward as possible, we have added a series of frequently asked questions below. \n\n\n\n[block:api-header]\n{\n  \"title\": \"Frequently Asked Questions\"\n}\n[/block]\n- My app uses GCM to send pushes from Pulsate, what do I need to do?\n\nTo ensure that you can continue to send push notifications to Android devices after April 11th, you will need to migrate from GCM to FCM. Google have provided a guide to migrate from FCM to GCM [here.](https://developers.google.com/cloud-messaging/android/android-migrate-fcm)\n\nWhen you have migrated to FCM, you will need to add your new FCM tokens to Pulsate via the instructions outlined [here.](https://pulsate.readme.io/docs/fcm-configuration).\n\n- When do I have to make this change?\n\nGoogle is deprecating GCM on April 11th, 2019. However, Pulsate will make the switch over to FCM from GCM on March 1st so all apps should be migrated from GCM to FCM by March 1st, 2019. \n\n- Will there be any functionality changes and will this effect the push notifications that my app sends? \n\nNo there will be no functionality changes and Android push notifications will remain exactly the same as if they were delivered by GCM. This includes full support for rich media images, buttons and inserting personalization tags. \n\n- What will happen if I don't migrate my GCM implementation to FCM before Pulsate changes on March 1st?\n\nFCM and GCM tokens are interchangeable and will both be accepted as valid by both services until April 11th when GCM support is deprecated by Google. From March 1st all future SDK versions and Pulsate updates will use FCM only. Between March 1st and April 11th push notifications should be able to be delivered using GCM tokens but Pulsate will not directly support this and Google may change this at any time. \n\nIt is highly recommended that every app using Pulsate migrates to FCM from GCM before March 1st. \n\n- What will happen if I don't migrate my GCM implementation to FCM before Google deprecates GCM on April 11th. \n\nIt is unlikely that any push notifications will be delivered to Android devices via GCM from April 11th onwards. \n\n- How can I test FCM before migrating to GCM? \n\nWe have released a beta version of the Android SDK with FCM support. You can access it by using the following dependency: \n\nimplementation  ‘com.pulsatehq.sdkbeta:PulsateSdk:2.14.0-beta-1’\n\n**This is a BETA release, DO NOT use it in App Releases.**","excerpt":"","slug":"migrating-from-gcm-to-fcm","type":"basic","title":"Migrating from GCM to FCM"}

Migrating from GCM to FCM


[block:callout] { "type": "success", "body": "Any apps that are integrating Pulsate for the first time should use our guide [here](https://pulsate.readme.io/docs/fcm-configuration) for configuring push notifications using Firebase Cloud Messaging (FCM)" } [/block] On the 11th of April, 2019, Google will be deprecating their Google Cloud Messaging service and anyone who wishes to send push notifications to Android devices will need to use Firebase Cloud Messaging (FCM). Pulsate has used GCM to deliver push notifications on Android up until this point and we will now be migrating over to support FCM instead. This will require all Pulsate clients who have an Android app to migrate to FCM as well. Google have provided a guide to migrate from FCM to GCM [here.](https://developers.google.com/cloud-messaging/android/android-migrate-fcm) Pulsate will be removing direct support for GCM on March 1st ahead of Google deprecating the GCM service on April 11th. Currently, FCM and GCM tokens are interchangeable and can be used to send pushes on either service. However, this is likely to change on April 11th so every developer will need to update their implementation to use FCM instead of GCM. To ensure the migration process is as straightforward as possible, we have added a series of frequently asked questions below. [block:api-header] { "title": "Frequently Asked Questions" } [/block] - My app uses GCM to send pushes from Pulsate, what do I need to do? To ensure that you can continue to send push notifications to Android devices after April 11th, you will need to migrate from GCM to FCM. Google have provided a guide to migrate from FCM to GCM [here.](https://developers.google.com/cloud-messaging/android/android-migrate-fcm) When you have migrated to FCM, you will need to add your new FCM tokens to Pulsate via the instructions outlined [here.](https://pulsate.readme.io/docs/fcm-configuration). - When do I have to make this change? Google is deprecating GCM on April 11th, 2019. However, Pulsate will make the switch over to FCM from GCM on March 1st so all apps should be migrated from GCM to FCM by March 1st, 2019. - Will there be any functionality changes and will this effect the push notifications that my app sends? No there will be no functionality changes and Android push notifications will remain exactly the same as if they were delivered by GCM. This includes full support for rich media images, buttons and inserting personalization tags. - What will happen if I don't migrate my GCM implementation to FCM before Pulsate changes on March 1st? FCM and GCM tokens are interchangeable and will both be accepted as valid by both services until April 11th when GCM support is deprecated by Google. From March 1st all future SDK versions and Pulsate updates will use FCM only. Between March 1st and April 11th push notifications should be able to be delivered using GCM tokens but Pulsate will not directly support this and Google may change this at any time. It is highly recommended that every app using Pulsate migrates to FCM from GCM before March 1st. - What will happen if I don't migrate my GCM implementation to FCM before Google deprecates GCM on April 11th. It is unlikely that any push notifications will be delivered to Android devices via GCM from April 11th onwards. - How can I test FCM before migrating to GCM? We have released a beta version of the Android SDK with FCM support. You can access it by using the following dependency: implementation ‘com.pulsatehq.sdkbeta:PulsateSdk:2.14.0-beta-1’ **This is a BETA release, DO NOT use it in App Releases.**