Identify the missing responsibility
| Symptom | Inspect first |
|---|---|
| Crashlytics classes unavailable to app code | Runtime dependency and source set |
| Reports arrive but release names are obfuscated | Mapping/build integration |
| Plugin cannot be resolved | Plugin version and repositories |
| Reports target the wrong Firebase app | Google services configuration and variant |
The setup guide gives the supported combination. Avoid copying a dependency coordinate into the plugin declaration block: those syntaxes are not interchangeable.
Use the BoM for supported runtime alignment
A module fragment can declare:
implementation(platform("com.google.firebase:firebase-bom:34.19.0"))
implementation("com.google.firebase:firebase-crashlytics")
This dated example uses the BoM listed on 22 September 2026. The release table remains the source for later version checks. The Gradle plugin has its own version and compatibility requirements.
Do not add KTX to fix an unrelated problem
Current Firebase guidance moves Kotlin users to main modules; old firebase-crashlytics-ktx examples should not be pasted into a new setup as a default dependency. A missing import may require a documented migration rather than restoring an unsupported module.
Inspect the selected release graph
Run a dependency report for the distributed variant. A transitive constraint or manually pinned library can affect the final SDK version. Keep one clear version-management strategy instead of forcing several Crashlytics coordinates independently.
Verify the full reporting path
Build, install, trigger a controlled test crash, relaunch and inspect the intended Firebase app. For optimized builds, check readable frames from the exact release mapping.
APKLint's Gradle Dependency Checker can help spot misplaced declarations or inconsistent configuration. It cannot confirm plugin execution in your environment or the arrival of a remote report, so retain actual build output and dashboard confirmation as separate evidence.
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
