Hacktoberfest 2026: những issue maintainer đã đánh dấu cho tháng Mười, đang mở và phù hợp người mới. Xem issue Hacktoberfest

[firebase_messaging]: Android: a burst of background messages starts a FlutterEngine per service start, and can lose all of them

Đang mở
  • Có gì không ổn?
#18,789 1 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

@SelaseKay đang làm issue này rồi.

Từ ngày 13/10/2026.

  • #18791 của @SelaseKay — đang mở

Đánh giá

Độ khó
1/5
Thời gian dự kiến
Dưới một giờ
Mức phù hợp với người mới
45/100
Loại issue
Lỗi
Độ rõ ràng
Đặc tả rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
android, dart, flutter
Lĩnh vực
backend, mobile

Hướng nghiên cứu

Read FlutterFirebaseMessagingBackgroundExecutor.java around line 140 and trace how startBackgroundIsolate() assigns the engine before the queued callback runs. Reproduce with a burst of background data messages on Android, then check that only one engine is created and every queued message is handled. The issue reports a one-line fix and a successful 12-message run, though it does not name a test file.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

Needs Attention platform: android plugin: messaging reproduced type: bug
Is there an existing issue for this?
  • I have searched the existing issues.
Which plugins are affected?

Messaging

Which platforms are affected?

Android

Description

When several data messages reach an app that isn't running (a device switched on, or back online, after missing a few), FlutterFirebaseMessagingBackgroundExecutor creates a background FlutterEngine for every FlutterFirebaseMessagingBackgroundService start that lands before the first engine exists, instead of one.

Expected: one background engine, and every message handled.

Actual: one engine per early service start. On a profile build, 12 messages held while the device was off, then boot: 6 × Creating background FlutterEngine instance. and 6 × FlutterFirebaseMessagingBackgroundService started! in one process. On a debug build, 22 held messages: 22 engines, then the low-memory killer, and no notification shown.

Cause: onCreate calls startBackgroundIsolate(), whose guard is if (backgroundFlutterEngine != null) return;. But the engine is only assigned inside the callback that method posts to the main looper after ensureInitializationCompleteAsync. Every service start before then posts another callback. The callback checks only isNotRunning(), which stays true until Dart sends MessagingBackground#initialized, so each one creates a new engine, overwrites backgroundFlutterEngine and backgroundChannel, and starts another isolate. The queued intents drain only in onInitialized. Their work was already completed, so if the process dies first (memory pressure from N engines) they are lost.

Fix (FlutterFirebaseMessagingBackgroundExecutor.java, L140 on 16.7.0 and on main at 90c22c8dd9):

-                if (isNotRunning()) {
+                if (isNotRunning() && backgroundFlutterEngine == null) {

onCreate, the posted runnable and its callback all run on the main looper, so once the first callback assigns the engine, every later one skips. With that change, the same 12-message boot burst makes one engine and shows all 12 notifications.

Reproducing the issue
  1. Register a handler with FirebaseMessaging.onBackgroundMessage.
  2. Power the device off.
  3. Send ≥10 high-priority, data-only messages to it.
  4. Boot the device without opening the app.
  5. Count Creating background FlutterEngine instance. in logcat: one per early service start, not one.

A profile or release build shows the duplicate engines cleanly. On a debug build the first engine's kernel load on the main thread (7–10 s) can also trip a background ANR on the pending FCM broadcast, which is a separate, debug-only effect.

Firebase Core version

4.15.0

Flutter Version

3.47.7

Relevant Log Output
# Profile build, 12 held data messages, device booted without opening the app (one process):
I FLTFireBGExecutor: Creating background FlutterEngine instance.     (×6)
I FLTFireMsgService: FlutterFirebaseMessagingBackgroundService started!     (×6)

# The same burst with the one-line fix:
I FLTFireBGExecutor: Creating background FlutterEngine instance.     (×1)
I FLTFireMsgService: FlutterFirebaseMessagingBackgroundService started!     (×1)
Flutter dependencies

firebase_messaging 16.7.0, firebase_core 4.15.0.

Additional context and comments
  • Versions: firebase_messaging 16.7.0 and main at 90c22c8dd9. Earlier 16.x releases (checked: 16.4.2, 16.4.3, 16.6.0) have the same isNotRunning()-only check in the callback.
  • Tested on an Android 16 emulator.
  • We're carrying the one-line change above as a build-time patch until a fix ships, and we're happy to open a PR with it if that helps.
Ngôn ngữ chính
Dart
Star
9.3k
Fork
4.1k
Merge trung bình
2 ngày 2 giờ
Pull request đã merge (30 ngày)
41

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của firebase/flutterfire

Tất cả issue của firebase/flutterfire

Issue tương tự

Thêm issue về Dart

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.