ClientLogin will be shut down for GCM

[Magnus Hyttsten]

Please observe that we will shut down ClientLogin (http://goo.gl/d4F6SF) access for GCM in July 2015. ClientLogin was officially deprecated (http://goo.gl/JdkDWh) on April 20, 2012, and will be shut down on April 20, 2015 (http://goo.gl/DkRZwW). Only GCM users can continue to use this service until July 2015.

We understand how important it is for your 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 Project Number, you will have to: 

1. Update the app and register with Project Number. The app on the device will receive a new registration ID. See Getting Started (http://goo.gl/Z6cWj9) on how to obtain Project Number.

2. Once your server has received the new registration ID, the server can stop authenticating itself using ClientLogin when trying to send GCM messages to the app on the device. You can find instruction on how to send GCM push messages without ClientLogin here (http://goo.gl/muQq1Q).

[Tomcat]

Has GCM ever been able to register w/o Project Number?

2015年3月10日火曜日 7時44分52秒 UTC+9 Magnus Hyttsten:

[Francesco]

Thanks Tomcat,

to clarify ClientLogin deprecation only affects C2DM users, not current GCM users.

So if you are still using the C2DM APIs with ClientLogin, be aware that after July, the calls to send messages will start to fail.

Thanks,

  f

--
You received this message because you are subscribed to the Google Groups "android-gcm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-gcm...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-gcm/db924dd9-d1d0-4366-8f01-ed7aebfc001a%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[KoSh KoSh]

i'm really trying to understand Android deprecation and how they work,  like for example instead of writing new stuff and using separate stuff for everything, why Android does not just update the current implementation of everything instead of creating new stuff? i really would like to know the cons and pros behind this mechanism. P.S i'm referring to general.  in my opinion that will be good reason for developers to not bother about making changes but focus more in new making new implementations. your answer is appreciated. 

[Tomcat]

Hi Francesco,

Thank you for complete answer. Now I clearly understood.

2015年3月11日水曜日 3時36分39秒 UTC+9 Francesco Nerieri:

[Michael Oki]

Thanks for the update.

@others If you need GCM assistance for your app...send me a mail.