firebase_messaging: We are experiencing an application crash on iOS when a remote notification is received.
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 42/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Ambito
- backend-api-design, mobile
Direzione di ricerca
Start by inspecting FLTFirebaseMessagingPlugin.m around line 518 and the application:didReceiveRemoteNotification:fetchCompletionHandler: callback, then trace how PushKit notifications reach it. The report lacks a complete dependency list and a minimal reproduction, so first compare the crash path with the plugin’s iOS notification handling and identify the failing message dispatch. Done means reproducing or isolating the crash and confirming a safe callback path with a regression test.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Is there an existing issue for this?
- I have searched the existing issues.
Which plugins are affected?
No response
Which platforms are affected?
iOS
Description
[REQUIRED] Environment info
firebase-tools: Not applicable (Issue related to Firebase Messaging Flutter plugin).
Platform: iOS (Flutter application)
Firebase Messaging: firebase_messaging 15.0.4
Flutter version: 3.44.3
iOS version: 27.0.1
[REQUIRED] Test case
We are experiencing an application crash on iOS when a remote notification is received.
The crash occurs on the main thread inside the Firebase Messaging Flutter plugin, specifically in the following method:
-[FLTFirebaseMessagingPlugin application:didReceiveRemoteNotification:fetchCompletionHandler:]
The crash stack trace indicates that the failure occurs while UIKit/PushKit is processing an incoming remote notification payload.
[REQUIRED] Actual behavior
The application crashes on the iOS main thread while processing an incoming remote notification.
The crash occurs inside the Firebase Messaging plugin at:
FLTFirebaseMessagingPlugin.m:518
The top-level exception points to objc_msgSend, suggesting that an Objective-C message dispatch is failing during notification processing.
This issue appears to involve the interaction between Firebase Messaging and PushKit notification handling.
We would appreciate help identifying the root cause and understanding whether this is a known issue with Firebase Messaging's iOS notification handling.
Reproducing the issue
[REQUIRED] Steps to reproduce
Integrate Firebase Messaging into a Flutter iOS application.
Configure remote push notification handling.
Send or receive a remote notification through the configured PushKit/notification flow.
When iOS invokes the remote notification callback, the application occasionally crashes on the main thread.
Crash logs consistently point to FLTFirebaseMessagingPlugin.m, specifically the application:didReceiveRemoteNotification:fetchCompletionHandler: method.
[REQUIRED] Expected behavior
Firebase Messaging should safely handle incoming remote notification payloads without causing an application crash.
The notification callback should complete successfully, and the application should continue running normally.
Firebase Core version
3.3.0
Flutter Version
3.44.3
Relevant Log Output
Crashed: com.apple.main-thread
0 libobjcMsgSend.dylib
objc_msgSend + 8
1 Runner
-[FLTFirebaseMessagingPlugin application:didReceiveRemoteNotification:fetchCompletionHandler:]
+ 518 (FLTFirebaseMessagingPlugin.m:518)
2 UIKitCore
-[UIApplication pushRegistry:didReceiveIncomingPushWithPayload:forType:withCompletionHandler:]
3 PushKit
-[PKPushRegistry remoteUserNotificationPayloadReceived:completionHandler:]
Flutter dependencies
Expand Flutter dependencies snippet
Replace this line with the contents of your `flutter pub deps -- --style=compact`.
Additional context and comments
No response
- Lingua principale
- Dart
- Stelle
- 9.3k
- Fork
- 4.1k
- Merge medio
- 1g 13h
- PR unite (30g)
- 70
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di firebase/flutterfire
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
firebase/flutterfire#18908 ·
I maintainer di solito rispondono entro 1 giorno
-
[📚] App Check Windows Support still N/A on ReadmeForse già presa @Adrianogba l’ha presa oggi. Apertagood first issue type: documentation
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 35/100
firebase/flutterfire#18913 ·
I maintainer di solito rispondono entro 1 giorno
-
[📚] Data Connect Windows Support still N/A on ReadmeForse già presa @Adrianogba l’ha presa oggi. Apertagood first issue type: documentation
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 35/100
firebase/flutterfire#18911 ·
I maintainer di solito rispondono entro 1 giorno
-
[📚] Realtime Database Windows Support still N/A on ReadmeForse già presa @Adrianogba l’ha presa oggi. Apertagood first issue type: documentation
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 1/100
firebase/flutterfire#18909 ·
I maintainer di solito rispondono entro 1 giorno
-
[cloud_firestore][Android]: query snapshots() can deliver an older snapshot after a newer one since 6.7.0Forse già presa @KafuiDumeloo l’ha presa 2 giorni fa. Aperta
Difficoltà 3/5 1-2 giorni Idoneità per principianti 45/100
firebase/flutterfire#18904 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di firebase/flutterfire
Issue simili
-
bug to check
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
I maintainer di solito rispondono entro 1 giorno
-
documentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
patarapolw/lingua_srs#103 ·
I maintainer di solito rispondono entro 1 giorno
-
[Feature]Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
I maintainer di solito rispondono entro 5 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
desktop linux photos
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno