[firebase_messaging]: FirebaseMessaging.onMessage not received any data
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- backend-api-design, mobile
Research direction
Start by checking the firebase_messaging iOS implementation around FLTFirebaseMessagingPlugin.configureNotificationCenterDelegate() and how foreground messages reach FirebaseMessaging.onMessage. Reproduce the report on an iOS simulator using the provided notification and data payload, then compare behavior with the banner presentation options. Done means identifying why the foreground callback receives no data and confirming the expected behavior with a focused regression test.
Written by the indexing model from the issue text.
Description
Is there an existing issue for this?
- I have searched the existing issues.
Are you aware of the differences between iOS and Android background message handling?
- I understand that iOS and Android background messages behave differently, and I've designed my application with that in mind.
Do you have an active Apple Developer account?
- I have an active Apple Developer account.
Are you using a physical iOS device to test background messages?
- I am using a physical iOS device to test background messages.
Have you enabled "Remote Notifications" & "Background Mode" (Checking options for "Background Processing" & "Remote Notifications") in your app's Xcode project?
iOS simulator issues
FirebaseMessaging.onMessage not working
version firebase_messaging: ^16.7.0
added FLTFirebaseMessagingPlugin.configureNotificationCenterDelegate()
Have you created an APNs key in your Apple Developer account & uploaded this APNs key to your Firebase console?
yes
Have you disabled method swizzling for Firebase in your app?
<array>
<string>UIInterfaceOrientationPortrait</string>
<string>UIInterfaceOrientationPortraitUpsideDown</string>
<string>UIInterfaceOrientationLandscapeLeft</string>
<string>UIInterfaceOrientationLandscapeRight</string>
</array>
<key>FirebaseAppDelegateProxyEnabled</key>
<true/>
Are you sending messages to your app from the Firebase Admin SDK?
{
message: {
token: token,
notification: {
title: notifTitle,
body: notifBody,
},
data: {
title: notifTitle,
body: notifBody,
thread_id: String(thread_id || ""),
type: String(type || "CHAT"),
//...data,
},
android: {
priority: "HIGH",
notification: {
title: notifTitle,
body: notifBody,
sound: "default",
channel_id: "bizcentre_omnichannel_channel",
notification_priority: "PRIORITY_MAX",
default_sound: true,
default_vibrate_timings: true,
visibility: "PUBLIC",
},
},
apns: {
headers: {
"apns-push-type": "alert",
"apns-priority": "10"
},
payload: {
aps: {
alert: {
title: notifTitle,
body: notifBody,
},
sound: "default",
badge: 1,
"content-available": 1,
'mutable-content': 1,
},
},
},
},
}
Have you requested permission from the user to receive notifications?
- I have the relevant permission to receive notifications.
Have you used the 'Console' application on your macOS device to check if the iOS device's system is throttling your background messages?
the banner shown if set
await FirebaseMessaging.instance.setForegroundNotificationPresentationOptions(
alert: true,
badge: true,
sound: true,
);
Additional context and comments
No response
- Dominant language
- Dart
- Stars
- 9.3k
- Forks
- 4.1k
- Avg merge
- 2d 18m
- Merged PRs (30d)
- 34
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from firebase/flutterfire
-
🚀 [firebase_core] Bump Firebase iOS SDK (12.19.0 → 13.0.0)Possibly taken @SelaseKay claimed this 5 days ago. OpenNeeds Attention platform: ios plugin: core type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
firebase/flutterfire#18769 · 2 comments ·
Maintainers usually reply within 1 day
-
🚀 [firebase_core] Bump Firebase Android SDK (34.19.0 → 35.0.0)Possibly taken @SelaseKay claimed this 5 days ago. OpenNeeds Attention platform: android plugin: core type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
firebase/flutterfire#18765 · 1 comment ·
Maintainers usually reply within 1 day
-
[cloud_firestore] Android: `FieldValue.arrayRemove` on nested maps blocks all Firestore calls for minutes (fixed by Firebase BoM 35)Possibly taken @SelaseKay claimed this 5 days ago. OpenNeeds Attention platform: android plugin: cloud_firestore type: bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
firebase/flutterfire#18781 ·
Maintainers usually reply within 1 day
-
🚀 [firebase_core] Bump Firebase JS SDK (12.19.0 → 13.0.0)Possibly taken @SelaseKay claimed this 5 days ago. OpenNeeds Attention platform: web plugin: core type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
firebase/flutterfire#18766 · 1 comment ·
Maintainers usually reply within 1 day
-
[📚] Remote Config Windows Support still N/A on ReadmePossibly taken @nightcityblade claimed this 5 days ago. Openblocked: customer-response good first issue Needs Attention platform: windows plugin: remote_config type: documentation
Difficulty 1/5 Under an hour Newbie friendliness 30/100
firebase/flutterfire#18763 · 3 comments ·
Maintainers usually reply within 1 day
All issues in firebase/flutterfire
Similar issues
-
discover
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
DevDogsUGA/DogPack#14 ·
-
direct-code
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
aaronified/fluenough#500 ·
Maintainers usually reply within 1 day
-
bug: native AES-CBC byte operations read mutated input after invocationPossibly taken @harrshita123 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
google/webcrypto.dart#436 · 1 comment ·
Maintainers usually reply within 7 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
openfoodfacts/smooth-app#7831 ·
Maintainers usually reply within 1 day