Hello, I'm developing a Communication app that uses GCM, to be able to wake
up from background or when app is killed by system for some reasons. My
problem is, when I send app to background and services being stopped, then
GCM notification is waking up the application, but for some reason if I
leave the phone for a long time in a different network conditions (network
changes from wifi to mobile, no network at all, etc) system is stopping
delivery of GCM messages to my app according to this logcat output.
*12-06 14:34:16.346 1418-1418/? W/GCM-DMM: broadcast intent callback:
result=CANCELLED forIntent { act=com.google.android.c2dm.intent.RECEIVE
flg=0x10000000 pkg=my_app_package_name (has extras) }*
At the same conditions other Communication apps like WhatsApp is able to
wake up, and System is delivering Notifications with ALLOW flag instead of
CANCELLED flag, and Intent is successfully passed to package.
So my question is, what can be causes for cancelling the Intent delivery to
the package?
I've implemented the GCM listeners and services according to google
gcm-sample, I have BOOT_COMPLETED receiver and STICKY service that can wake
up the app. The device are XIAOMI REDMI NOTE 3, SAMSUNG GALAXY S6.
Best Regards.
P.S. Sorry for my bad English.
--
You received this message because you are subscribed to the Google Groups
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/android-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/android-developers/a17a6c5c-7e0f-4a3e-8ecc-4d1efcd64276%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
