well..that will really awesome!!!
To add some perspective -- this is not only an awesome feature but a requirement by Google:
According to this, the gcm.register is deprecated since May 2015:
GCM register() is deprecated starting May 28, 2015. New app development should use the Instance ID API to handle the creation, rotation, and updating of registration tokens.
While there do not seem to be direct implications (it still works), it would be prudent to plan for migration for the day will come when GCM stops accepting new register() calls.
@miraculixx Agreed, that's why I'm working on it. 😺
@macdonst glad to hear 👍 thanks
Anyone who wants to test it can check out branch issue188. It seems to be working just fine but I need to do more testing.
Issue #188: Use Google's InstanceID API
Implement GCM Clould Messaging
Implement Token Refresh Listener
Update Android compilation instructions
Fix committed will be official in 1.4.0 release.
Thanks @macdonst ! 👍
Can you please also update the README.md file to reflect the changes on how to use it. 😃
@bhaveshgohel I already did under Android compilation. No changes to JS code are necessary.
Ohh... Thanks @macdonst! 😃
It added the "Find accounts on the device" Contact permission. What is that permission used for, if it's used?
@jayj Hmm...that is Google Play Services adding that. Lemme see if I can make that smaller.
Fixes for using new GcmReceiver code
Replace intent category "com.example.gcm" with $PACKAGE_NAME in plugin.xml.
Change play services dependancy to more specific play-services-gcm
update issue #188
@jayj I just merged a PR from contributor @smdvdsn that should remove the need for the "Find accounts on device" permission.