question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

GCM-DMM : broadcast intent callback: result=CANCELLED

See original GitHub issue

I can receive FCM Remote push notification when I boot my phone and actually open the app. I receive the notifications if the app is in the foreground or background as expected. However, I expect to also receive the push notifications if the user has not yet opened the app. I do not receive these notifications, in other words, when the app is killed or has not yet been opened.

In my logcat I see the following error:

GCM-DMM : broadcast intent callback: result=CANCELLED forIntent
{ act=com.google.android.c2dm.intent.RECEIVE flg=0x10000000 pkg=com.lisdo (has extras) }

After googling I came across this question.

It suggests, that in the AndroidManifest.xml something is missing to register these FCM events, but I thought the steps in the READ.ME would cover this scenario.

Any ideas??

I am running on an actual android device for testing (Xiaomi Mi Mix) and I do receive remote PN from other apps (WhatsApp, etc.).

"react-native": "^0.47.1",
"react-native-fcm": "^13.3.3",

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:14 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
Xing1Pcommented, Mar 26, 2019

try this

<permission android:name="${applicationId}.permission.C2D_MESSAGE" android:protectionLevel="signature" />
    <uses-permission android:name="${applicationId}.permission.C2D_MESSAGE" />
1reaction
evollucommented, Mar 6, 2018

seems right to me. also try to reproduce in android emulator

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error broadcast intent callback: result=CANCELLED forIntent ...
This error appears when I send a push notification through GCM, in a real device, and the app has not been started yet...
Read more >
Device receives GCM intent, but fails to launch application.
03-30 19:43:24.606: W/GCM-DMM(4931): broadcast intent callback: result=CANCELLED forIntent { act=com.google.android.c2dm.intent.
Read more >
Problem with GCM push while application is paused
W/GCM/DMM ( 899): broadcast intent callback: result=CANCELLED forIntent { act=com.google.android.c2dm.intent.RECEIVE pkg=com.thammit.pushtest (has extras) }.
Read more >
Not receiving push notifcation after app is killed - Pushwoosh
Hi, I'm trying to figure out why my app isn't receiving push notifications when the app is killed. So when the app is...
Read more >
Android – Error broadcast intent callback: result=CANCELLED ...
This error appears when I send a push notification via python. 09-13 21:21:44.800 1851-1851/? W/GCM-DMM: broadcast intent callback: result=CANCELLED forIntent ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found