I am starting to implement google cloud messaging into my app and have some worries regarding the deprecation of old device registration procedures.
In all the examples in the forum the device demo broadcasts a com.google.android.c2dm.intent.REGISTER intent to get the registration ID. I have looked at the google documentation and this method is not mentioned anywhere anymore. The old docs say you should use GCM.Register() to obtain the registration id/token, the service part seems to be the same as in the examples.
Last month however google has changed all the documentation and examples regarding device registration and receiving of messages. New documentation for the device part is here:
Implementing GCM Client on Android
We are now required to use InstanceID API (which requires Google play services, as does the GCM API) to obtain registration tokens, implement GcmReceiver to receive messages, GcmListenerService to process messages and InstanceIDListenerService to handle creation, rotation and updating of registration tokens.
I would very much like to hear your thoughts on this as I would not want to implement something that will stop working on the 30th of July when C2DM is turned off by google or six months later when google decides to turn off the old registration procedures.
Your thoughts are appreciated.
Erel if you are by any chance already looking into this please let me know.
In all the examples in the forum the device demo broadcasts a com.google.android.c2dm.intent.REGISTER intent to get the registration ID. I have looked at the google documentation and this method is not mentioned anywhere anymore. The old docs say you should use GCM.Register() to obtain the registration id/token, the service part seems to be the same as in the examples.
Last month however google has changed all the documentation and examples regarding device registration and receiving of messages. New documentation for the device part is here:
Implementing GCM Client on Android
We are now required to use InstanceID API (which requires Google play services, as does the GCM API) to obtain registration tokens, implement GcmReceiver to receive messages, GcmListenerService to process messages and InstanceIDListenerService to handle creation, rotation and updating of registration tokens.
I would very much like to hear your thoughts on this as I would not want to implement something that will stop working on the 30th of July when C2DM is turned off by google or six months later when google decides to turn off the old registration procedures.
Your thoughts are appreciated.
Erel if you are by any chance already looking into this please let me know.
Last edited: