🐛 [Android] Firebase connection broken on BoM 4.10.0+ (regression from 4.9.0)

[DavidPluxia]

Bug report

Description

After upgrading FlutterFire packages from BoM 4.9.0 to BoM 4.10.0 or 4.11.0, our Android app no longer connects to Firebase correctly. Reverting to BoM 4.9.0 immediately resolves the issue.

This is related to #11146 and firebase/firebase-android-sdk#5101, but the symptoms are broader than stale snapshot listeners after background resume. On BoM 4.10.0+, the Android Firebase connection fails outright rather than just exhibiting stale data after extended backgrounding.

Steps to reproduce

1. Start with a working Flutter app using FlutterFire BoM 4.9.0 (firebase_core 4.4.0)
2. Upgrade all FlutterFire packages to BoM 4.11.0 (firebase_core 4.6.0)
3. Run on Android device
4. Observe Firebase connection failure

Expected behavior

Firebase should connect and function identically to BoM 4.9.0.

Actual behavior

Android app does not connect to Firebase correctly on BoM 4.10.0+. Works fine on BoM 4.9.0.

iOS is unaffected.

Environment

Flutter 3.41.5 • channel stable
Framework • revision 2c9eb20739 (2026-03-17)
Engine • revision 052f31d115
Dart 3.11.3

Android:

• minSdk: 29

FlutterFire packages (working on 4.9.0, broken on 4.11.0):

Package	Working (4.9.0)	Broken (4.11.0)
firebase_core	4.4.0	4.6.0
firebase_auth	6.1.4	6.3.0
cloud_firestore	6.1.2	6.2.0
cloud_functions	6.0.6	6.1.0
firebase_app_check	0.4.1+4	0.4.2
firebase_crashlytics	5.0.7	5.1.0
firebase_analytics	12.1.2	12.2.0
firebase_messaging	16.1.1	16.1.3
firebase_performance	0.11.1+4	0.11.2

Workaround

Pin all FlutterFire packages to BoM 4.9.0 versions.

Related issues

• 🐛 Firestore Snapshot Listeners Attaching Before ID Token Refresh, Resulting in Stale Data #11146 (Firestore snapshot listeners attaching before ID token refresh)
• Firestore is not picking up fresh auth token and reinitialising event listeners when the current token is stale. firebase-android-sdk#5101 (Firestore not picking up fresh auth token)