onMessageRecieved not working when app is killed. Any solution?

[KORuL]

Step 1: Describe your environment

• Android device: Meizu M1 Note
• Android OS version: 5.1
• Google Play Services version: com.google.gms:google-services:4.2.0
• Firebase/Play Services SDK version:

    implementation 'com.google.firebase:firebase-core:16.0.7'
//    implementation 'com.google.firebase:firebase-iid:17.1.0'
    implementation 'com.google.firebase:firebase-messaging:17.4.0'
    implementation 'com.firebase:firebase-jobdispatcher:0.8.5'
    implementation 'com.google.firebase:firebase-functions:16.1.3'
    implementation 'com.google.firebase:firebase-auth:16.1.0'
    implementation 'com.google.firebase:firebase-database:16.0.6'
    implementation 'com.google.firebase:firebase-crash:16.2.1'
    implementation 'com.google.firebase:firebase-storage:16.0.5'
    implementation 'com.google.android.gms:play-services-auth:16.0.1'
    implementation 'com.google.gms:google-services:4.2.0'
  

Step 2: Describe the problem:

Almost all phones are fine. But in some phone (Meizu M1 note):

onMessageRecieved not working when app is killed in some devices. It works perfect in foreground and in background. But when app is killed I don t receive notification in system tray, or call onMessageRecieved .

I send only DATA (to, data) notification. What I do wrong?

I read #4 , #89 , #86 , #368 , #365 , #337 , #205 , #96 , #20 , #4, #151 , #816 did not find the answer.

I get a strange error in logcat W/GCM: broadcast intent callback: result=CANCELLED forIntent { act=com.google.android.c2dm.intent.RECEIVE pkg=net.korul.hbbft (has extras) }

I made this receiver - but it did not help

<receiver
            android:name=".MyBroadcastReceiver"
            android:permission="com.google.android.c2dm.permission.SEND" >
            <intent-filter>
                <action android:name="com.google.android.c2dm.intent.RECEIVE" />
                <category android:name="net.korul.hbbft" />
            </intent-filter>
        </receiver>

AndroidManifest contains:

        <service android:name=".services.MyFirebaseMessagingService"
                 android:permission="true"
                 ndroid:stopWithTask="false">
            <intent-filter>
                <action android:name="com.google.firebase. MESSAGING_EVENT"/>
            </intent-filter>
        </service>

MyFirebaseMessagingService - is standart from snippset

Steps to reproduce:

1. Minimize and swipe out your application
2. Send FCM notification
3. You can see the below log but notification doesn't trigge

Observed Results:

W/GCM: broadcast intent callback: result=CANCELLED forIntent { act=com.google.android.c2dm.intent.RECEIVE pkg=net.korul.hbbft (has extras) }

Expected Results:

Should get the notification

Relevant Code:

I read all the branches dedicated to this issue, do not refer to them! The problem is, she is over 2 years old! Need a solution!

I also tried to send a push message with the firebase console, and it does not come - the exact same error

[google-oss-bot]

This issue does not seem to follow the issue template. Make sure you provide all the required information.

[samtstern]

@KORuL thank you for reading all of those other issues. It may very well be that Meizu has device-specific behavior changes which break FCM. Does this happen for you on other manufacturer's devices like Samsung or Google?

@kroikie do you think there is anything different going on here versus the other issues?

[KORuL]

This does not happen with Google and Samsung devices.
But how can I deal with those who do not come pushes? Do I have to hang in the form of service and put the battery? Or are there other ways? How to implement your own, for example, messenger if you don’t get it?

[jshandorov1]

Hello,
Exactly the same behaviour on my Huawei P20 Pro + Android 9. Just I have to wait ~12 hours and app gets optimized automatically. No notifications are received after this.

[EdwardQuixote]

I get the same problem on a Tecno Spark:

• Model: K7
• Android 7.0

Even worse is how, the app is in the "Recent Apps" list, but still doesn't get any push messages when it gets into Doze. Please note I'm using FCM High Priority Messages and I'm sending a data type of message.

I tried out other push notification services on the same device and I noticed one of the services, does restart it's notification listening service even when a user kills the App:

W/ActivityManager: Scheduling restart of crashed service me.pushy.example/me.pushy.sdk.services.PushySocketService in 1000ms
D/ActivityManager: AMS: *** Restart service me.pushy.example/me.pushy.sdk.services.PushySocketService
D/ActivityManager: AMS: Service me.pushy.example/me.pushy.sdk.services.PushySocketService is called by self.

Q) Is it possible to have such an implementation on FCM, regardless of the device?

[samtstern]

@EdwardQuixote just FYI the "pushy" service does not use FCM it uses its own MQTT-based push notification service so it has totally different properties.

[KORuL]

@samtstern Thank you, I will look at this library! It’s a pity that @google @samtstern doesn’t want to do anything with an obvious BAG, which has been preventing us from developing good applications for more than 2 years!

[EdwardQuixote]

@samtstern Yes it uses MQTT. I just thought maybe Google could give us something like it even if FCM uses different protocols.

[samtstern]

@EdwardQuixote that's a reasonable thing to ask, I was just saying that there's no need for us to do something like "restart the service" since FCM messages are received by Google Play services and not your app itself. When you use something like Pushy then each app is going to keep its own connection open. So that's where the different behavior comes from. If every app on your phone had an MQTT connection open in the background your battery would be very unhappy :-)

[KORuL]

@samtstern Why, then, Google will not fix this bug? Accepts push with google service and redirects the receiver in the application. It's good if all the push messages are handled by one service in the system, and only it keeps one connection for all. And yes, if each application opens the connection it will be bad. But what to do in this situation? Push is required when the application is closed!
I don’t like the answer of Google, from the category - we are fine on a pixel and samsung, so leave us alone! This is not an answer! Does not work on many phones!

[bsonmez]

It's bizarre. It works correctly android eight on a real device, and Android nine on a simulator, however, doesn't work on an actual device with android six unless it works on background. When the app killed by the user, doesn't receive messages.

[rayworks]

Got the same issue on Nokia TA-1000 OS 9.0 with
com.google.gms:google-services:4.2.0
com.google.firebase:firebase-messaging:17.4.0

W/GCM: broadcast intent callback: result=CANCELLED forIntent { act=com.google.android.c2dm.intent.RECEIVE pkg="app-pkg-name" (has extras) }

Also failed on SAMSUNG-G9300 (8.0.0) with an extra info :
D/MARsPolicyManager: Package: app-pkg-name, userid: 0, hostingType: broadcast is Restricted by policy: autorun(2) caller is: ProcessRecord{1e82998 19971:com.google.android.gms.persistent/u0a188}

W/GCM: broadcast intent callback: result=CANCELLED forIntent { act=com.google.android.c2dm.intent.RECEIVE flg=0x10000000 pkg="app-pkg-name" (has extras) }

However, it succeeded on Nexus 6P (OS 8.0), receiving the msg instantly. You could also check out this thread.

[montaqa]

i believe this has nothing to do with FCM, it is a service at the end of the day and you need to look on how to maintain a service from being killed by the OS and you will find a lot by googling on this.