Read the BoM as a compatibility map
The release notes show which product versions each BoM selects. A BoM number is not the version number of every Firebase SDK.
For example, a project can pin the BoM and omit a separate version on supported product dependencies:
implementation(platform("com.google.firebase:firebase-bom:34.19.0"))
implementation("com.google.firebase:firebase-crashlytics")
The BoM does not automatically install every product. The second declaration still matters.
Separate library and plugin updates
| Component | Managed by the Firebase Android BoM? |
|---|---|
| Supported Firebase product libraries | Yes, through version constraints |
| Google services Gradle plugin | No |
| Crashlytics Gradle plugin | No |
| Android Gradle Plugin and Gradle | No |
The setup documentation shows where these pieces belong. Updating the BoM does not fix every plugin compatibility problem.
Inspect the resolved graph
A manually specified product version or another constraint can alter resolution. Use the module's dependency report to confirm the actual selected versions rather than reading only the declaration.
Record the old and new BoM, changed products, minimum platform requirements and relevant release-note changes. A blanket “update everything” commit makes regressions harder to isolate.
Avoid dynamic production versions
A moving version selector can change a release build without a source change. Prefer a reviewed pinned version, committed dependency metadata and a reproducible CI environment.
Test authentication, database access, notifications and crash reporting only for the products your app actually uses. A successful Gradle sync is not a runtime compatibility test.
Use the scanner for inventory, not freshness guarantees
APKLint can support Firebase configuration inspection and build review. It cannot infer every transitive SDK version from a partial configuration file or automatically certify that your chosen BoM is still current. Recheck the official release table when planning the upgrade and retain that verification date with the release.
Sources and further reading
Reference review: 22 September 2026. Examples illustrate the workflow; check your installed versions, release artifact and account-specific Console requirements before applying them. This guide is not a claim that APKLint executed your project or verified your private account.
Android inspection tools and practical release guides. About APKLint · Report a correction
