Find all legacy declarations
Search module build files, version catalogs, convention plugins and shared dependency bundles for Firebase coordinates ending in -ktx. The Android release notes identify the change and link the migration guidance.
A top-level BoM update may leave an explicitly versioned old KTX module in the resolved graph, so inspect resolution as well as source text.
Replace the module deliberately
For example, migrate the dependency from the old Crashlytics KTX module to the supported main module under the chosen BoM:
implementation(platform("com.google.firebase:firebase-bom:34.19.0"))
implementation("com.google.firebase:firebase-crashlytics")
This is a dated dependency fragment, not a complete migration for every Firebase product. Follow the current setup guide and product-specific import/API instructions.
Fix imports without restoring obsolete modules
Kotlin extension availability and import paths should follow the main-module migration documentation. An unresolved import after removing a legacy dependency is a migration task, not a reason to silently re-add the unsupported artifact.
Separate source migration from unrelated architectural refactoring so failures remain easy to trace.
Verify the selected product versions
| Check | Expected evidence |
|---|---|
| Build declarations | Main modules used intentionally |
| Resolved graph | No accidental old KTX dependency retained |
| Compilation | Updated imports and API usage |
| Runtime | Product-specific flows still work |
Test only the products the app actually uses, including release optimization where relevant.
Keep plugin versions independent
The Firebase BoM does not manage every Gradle plugin. Review Google services, Crashlytics and Performance plugin compatibility separately when they are present.
APKLint's Gradle tools can support a search for legacy coordinates and inconsistent declarations. They cannot prove that every module or convention plugin has migrated, so retain the complete dependency report and runtime test results with the change.
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
