-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[firebase_messaging]: Only notification shown, no callbacks #17207
Comments
Thank you for providing detailed information about the issue. To better understand and debug the problem, it would be extremely helpful if you could create a minimal reproducible example that demonstrates the issue. This will allow us to isolate the problem and test potential solutions more effectively. Here are a few suggestions for the minimal example:
Additionally, since this issue involves VoIP calls on Android, I recommend considering the use of Android's Telecom Library for handling VoIP calls. This library is designed to integrate VoIP calls more seamlessly with the Android system, ensuring better compatibility and reliability. You can find more information in the official Android documentation. |
Hi! Thank you for the link to Android's Telecom Library! We're aware of that functionality but it does not fit too well with our use case, unfortunately. |
I have the same issue. i'm going to write a report issue and i see this thread FirebaseMessaging
|
same issues here. |
Hi everyone, it looks like the workaround for this issue is opting out of Google Play Services notification delegation, as mentioned in @hussenIbrahim's linked comment. Could anyone confirm if this solution works for them? |
I'm currently rolling out a version to beta users to test this. Will keep you posted if it works! |
I am also experiencing the issue where RemoteMessage is being delivered as null on my Galaxy S25 Ultra. |
Can confirm that the issue is, at least for my users, solved with deactivating delegation! I achieved this by adding these lines in the inside of my <meta-data
android:name="delivery_metrics_exported_to_big_query_enabled"
android:value="false" />
<meta-data
android:name="firebase_messaging_notification_delegation_enabled"
android:value="false" /> Those lines go into the For me, this issue is thereby completed but I think it would make sense to add some documentation somewhere to not let others fall into the same trap! |
Is there an existing issue for this?
Which plugins are affected?
Messaging
Which platforms are affected?
Android
Description
For a small set of my users, push message processing does not work as expected: When a push message comes in while the app is in background / screen is off, the device will wake up but only show the system notification. The notification sound of the referenced notification channel will play once but then the screen will turn off again and phone goes back to sleep.
What should happen would be a call to
onBackgroundMessage
so that my code can do additional things, like bringing the app to front and do a lot more ringing (the push message is for incoming VoIP calls).Then, even when the user taps the system notification to open the app, it will open but
onMessageOpenedApp
will not be called andgetInitialMessage
will delivernull
.The weird thing is that this only happens for a subset of devices with no discernible features (seen on Android 12 to 14 devices of various makes (Google Pixel, Samsung S series, Spectralink, ..) - but for those devices it's quite permanent: The issue will happen for every push message, and not go away when re-booting the phone, or re-installing the app.
I've already checked:
Also, I've dug a bit into the source code of the flutterfire source code, and if I understand correctly, the first Log message that I should see for every push notification would be from this line in
FlutterFirebaseMessagingReceiver
:On devices where the issue is present, I do not see this log message in system bug reports, in other devices, I can see it. So maybe this is an issue of the Google Play Services?
Any recommendation of where to continue debugging would be greatly appreciated!
Reproducing the issue
Unfortunately I can not provide such an example. The issue only appeared on devices of a few users; none are under my control and I'll not be able to convince them to install test apps for test pushes.
Firebase Core version
3.10.1
Flutter Version
3.27.0
Relevant Log Output
Flutter dependencies
Expand
Flutter dependencies
snippetAdditional context and comments
No response
The text was updated successfully, but these errors were encountered: