If you use Google Cloud Messaging (GCM), please note that ClientLogin has now been shut down
). This is a followup post from an advance notice we sent out in March. ClientLogin was officially deprecated (http://goo.gl/KGbhfG
) on April 20, 2012, and was shut down on April 20, 2015 (http://goo.gl/wrT5Jz
). Since then, only GCM users have been able to use this service, but that is also ending now.
We understand how important it is for you to connect with your users’ Android devices, so if your server is using ClientLogin to authenticate itself and your app is currently registering with GCM without using Sender ID, you will have to follow these steps:
1. Update the app and register with Sender ID. The app on the device will receive a new registration token. See Getting Started for the respective platforms on how to obtain a Sender ID:
2. Once your server has received the new registration token, the server can stop authenticating itself using ClientLogin when trying to send GCM messages to the app on the device. You can find instructions on how to send GCM push messages without ClientLogin here for HTTP (https://goo.gl/635Xkn
) and here for XMPP (https://goo.gl/Xj47TC