-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Notifications don't appear when the app is not running in the background #211
Comments
@vikasing the app should now get launched when a notification is received. On Android when the app is in the background the notification should show up in the notification shade. Are you seeing the message in the notification shade? |
When I stop the app by swiping left I don't get a notification, although notification is received by the device, (see above logcat entries). This has something to do with the intent flag 'FLAG_INCLUDE_STOPPED_PACKAGES', link to the discussion https://groups.google.com/forum/#!topic/android-gcm/MqVlA3Sj26c I have added this flag inside the onReceive method of GCMBroadcastReceiver.java inside gcm.jar, testing it right now. |
@vikasing Yes, please let me know how your testing goes. I'm not sure if adding that flag will help, what I think needs to happen is for the service to restart itself if killed. Yup, if you look at branch |
The flag seems to help, I'm getting the notifications consistently, even Good to hear about play services integration.
|
@vikasing you wanna do a PR to include that flag? I love to get contributions from others. |
Created a PR, but I'm not sure whether this can be merged without removing gcm.jar dependency from the plugin because now gcm.jar files are present in src directory. |
@vikasing yeah, that PR can't be merged as gcm.jar was removed from the pluing. |
Hi I have the same problem on my application. Push notification is arrive if the application is open in foreground or background but if i force kill the app the notification didn't appear even in notifications. When i checked the logcat i saw this message: I/GCM ( 6639): GCM message com.mobile.adMingle 0:1456297445266991%b1acb7f0f9fd7ecd I already check @vikasing 's codes on my plugin resource but i couldn't find it on the latest version of my downloaded plugin (1.5.3 version) Can you please assist me what should i do? |
+1 Having same issue here. Why is this issue closed? Avoiding that flag proposal, are there any choices or updates on this? |
+1 I don't receive any notifications to my android but ios works fine Payload:
Some logcats
Android: 4.4.2, 5.0.1, 6.0.0 |
any solution for this? my android 6.0.1 Thanks |
I am receiving same issue for FCM |
Anyone got this figured?? brain-dead from not finding a solution 0_0 EDIT: link: what to do about it? well.... nothing i can figure :( |
HI! I'm having the same issue: However, on my add it works, but on my two mobile devices (one Huawei and a Cubox) it doesn't't work. How did you solve it? Thanks in advance! |
I have the exact same issue.. The notification does not show up in the notification shade, but I do get to see the notification arriving in logcat:
I'm testing on a Galaxy SII and a Nexus7, with the same result. Notifications work fine when the app is in background and foreground, just not when the app was force closed. I'm not sure if the problem comes from my payload structure:
or something to do with my Manifest File:
I'm really stuck on this one... would really appreciate some help! Thanks in advance |
@rjgpereira that is #158 in a nutshell |
@PaoloApplingua I'm experiencing this behaviour on Galaxy S2, Nexus 7 and also on a Wiko. So, I don't think that's the problem here. @macdonst I just don't get that thread. Most of the people are reporting problems with the notification event not being triggered, but they seem to be having the notification displayed in the notification area, which is not my case. |
This thread has been automatically locked. |
Sometimes notifications don't appear when the app is not running in the background. I can see notifications are getting delivered to the device in logcat, but the app fails to launch:
10-07 23:01:00.035 840-840/? D/StatusBar.Clock: Receive ACTION_TIME_TICK
10-07 23:01:04.144 1198-25021/? I/GCM: GCM message com.example 0:1444239064801662%5866dd3001bf28ae
10-07 23:01:04.166 671-693/? W/BroadcastQueue: Reject to launch app com.example/10230 for broadcast: App Op 48
10-07 23:01:04.170 1198-1198/? W/GCM-DMM: broadcast intent callback: result=CANCELLED forIntent { act=com.google.android.c2dm.intent.RECEIVE pkg=com.example (has extras) }
The text was updated successfully, but these errors were encountered: