Open stkq opened 6 years ago
Hi @stkq couple questions:
We are having the same issue, and it is a major problem. Any forecast on when is it going to be resolved? Any workaround?
We have same issues with our test devices. Seems like some device manufacturers don't allow notifications in some situations, We are investigating also Take a loook on manufacturers-interfere-with-reliable-notifications
Hi. We have same issue even in release builds. According to FCM diagnostic tool we found out that we received all messages but some of them weren't broadcasted to our app. Any thoughts how to deal with it? To be clear:
Im not a bot I just don't talk
I am also working on a calling app, and I am still dealing with the same issue. For me there are random periods of a minute or two where no notifications arrive, and then it works again. For a calling app that is not fine. Did you ever find a work around for this problem @memfis19 ?
The onMessageReceived method is only called for about 2/3 of the users. It's not because it's in the background because it's a data payload sent from Microsoft Azure, and the method is called for me and the notification displayed when I have the app closed. I know they're reaching the device because I checked the Play Console and they're marked as 'Acknowledged'.
Steps to reproduce:
Observed Results:
Only about 2/3 of the notifications end up with a call to onMessageReceived.
Expected Results:
I expected all of the notifications to reach onMessageReceived.
Relevant Code: