Published November 22, 2026

Firebase BoM 5.2.0 Raises the Flutter Floor to 3.44 and Makes AI Plugins Wasm-Ready

Flutter BoM 5.2.0 landed on November 16, 2026. The headline in the release notes is the line every team should read first: no packages with breaking changes. That is true, and it is also a little misleading, because the bill of materials quietly raised the floor on the Flutter and Dart versions it will resolve against, which is the kind of change that breaks a build without breaking an API.

Every plugin in the release now declares Dart ^3.12.0 and Flutter >=3.44.0. In BoM 5.1.0, published on October 22, those numbers were Dart ^3.6.0 and Flutter >=3.27.0. A project pinned to Flutter 3.41 or 3.38 cannot resolve this set at all, and pub will tell you so in the least helpful way possible, usually by failing on a transitive FlutterFire dependency you never named yourself.

Why the floor moved four releases in one jump

The changelog explains the jump without ever stating it as policy. Two Android entries repeat across almost every plugin: migrate plugins to built-in Kotlin on Flutter 3.44, and detect built-in Kotlin instead of checking the AGP version. Flutter 3.44 changed how Android plugin subprojects obtain the Kotlin toolchain, and the Firebase plugins now depend on that behavior rather than inferring it from a Gradle plugin version number.

The practical effect is that a Flutter project older than 3.44 will not only refuse to resolve the package set. Force the versions and the Android build fails on Kotlin plugin resolution instead. Teams mid-migration should stay on BoM 5.1.0 until the framework upgrade is done, then move forward in one step.

The underlying platform SDKs moved too, and those numbers travel with the release regardless of which Flutter version you run:

  • Firebase Android SDK 35.2.0, up from 35.1.0.
  • Firebase Apple SDKs 12.19.3 and 13.2.0.
  • Firebase JavaScript SDK 13.3.0, up from 13.1.0.
  • Firebase Windows SDK 14.1.0, unchanged since 5.1.0.

The AI plugins now have a Wasm guarantee

The most forward-looking entry belongs to firebase_ai and firebase_data_connect: both are now Wasm-ready, and CI checks the is:wasm-ready tag on every run. Flutter 3.50 made measurable Wasm gains on Safari and Firefox, and 3.51 is already in beta, but a web build is only as portable as its least portable dependency. Firebase AI Logic sat on the wrong side of that line until now.

Three parsing fixes round out the AI work: an omitted Vertex countTokens total now defaults to zero instead of throwing, URL retrieval responses without a status field still parse, and code execution results that omit their output no longer fail the whole response. Those read like edge cases until you remember that a model produces them at random. A production app talking to a remote model needs every one handled, because the alternative is a crash on a response nobody can reproduce locally.

Firestore finishes its move to Swift

Cloud Firestore 7.2.0 migrates the iOS and macOS plugin implementation to Swift. This is the same direction the whole ecosystem has been traveling since Flutter 3.44 made Swift Package Manager the default for Apple platforms, and it lands weeks before the CocoaPods trunk goes read-only in December. Plugin authors who still maintain an Objective-C podspec should treat the Firestore migration as the reference implementation.

Ordering also changed in a way that will be visible to anyone with a listener on a query. Query snapshots are now delivered before the snapshotsInSync callback fires, so the sync signal no longer arrives ahead of the data it is supposed to signal. If you were using snapshotsInSync as a proxy for first paint, that assumption was wrong before and is now simply impossible.

The remaining Firestore fixes are platform-specific and unglamorous. The Windows codec forwards persistenceEnabled instead of dropping it. A Windows transaction that times out now fails cleanly rather than touching a destroyed object. Apple platforms drop snapshot events that were queued after a cancel.

Messaging, auth, and functions

Cloud Messaging 17.1.0 carries the largest list of behavioral corrections:

  • The Android background service is skipped entirely when no handler is registered, instead of starting and idling.
  • iOS reads the APNs token type from the provisioning profile rather than assuming one.
  • Android releases the FCM run wake lock off the main thread.
  • Broadcasts that carry no message are ignored.
  • Every foreground message reaches onMessage exactly once, closing a duplicate delivery path.

Authentication 7.1.0 keeps the Auth error code when a token refresh fails, so a revoked credential no longer surfaces as a generic failure. Sign in with Apple state is cleared when the request ends. The web Auth emulator survives a browser restart. And sign-in redirect URLs are kept out of Flutter deep linking, which ends a class of bug where an OAuth return trip landed on a route handler instead of the auth SDK.

Cloud Functions 7.1.0 surfaces stream errors from httpsCallable as FirebaseFunctionsException, so a failed streaming call can be caught with the same error type as a unary one.

How to take the upgrade

Start by confirming the framework version. If flutter --version reports anything below 3.44, this BoM is not for you yet. Once on 3.44 or newer, bump the BoM, run a full pub upgrade rather than a targeted one, then rebuild the iOS app with Swift Package Manager enabled so the Swift Firestore implementation is what compiles.

After the build, test the three behaviors that changed most quietly: a Firestore listener that relies on snapshotsInSync ordering, an Android messaging flow with no background handler registered, and any OAuth redirect that previously landed in deep linking. None will fail to compile, and all three will look different at runtime.

The absence of breaking changes in this BoM is accurate and worth trusting. It just describes the API surface, not the floor beneath it.