Configure the build and runtime pieces
The Crashlytics setup guide distinguishes the runtime SDK from the Gradle plugin. The SDK records reports; build integration supplies release-related information such as mappings where applicable.
On 22 September 2026, the release notes list Crashlytics Gradle plugin 3.0.8 and Android SDK 20.1.1. Prefer the documented compatible setup, using the BoM for supported runtime dependencies rather than assuming plugin and SDK versions must match.
Apply configuration to the correct module
Check the application module, selected flavor, Google services configuration and Firebase app ID. A plugin applied only to a root project or a different module may not configure the artifact being distributed.
Keep development and production Firebase destinations explicit. Reports arriving in the wrong project can look like a delivery failure when the real issue is configuration selection.
Prove a controlled crash
Follow the official test-crash procedure. Use a development or internal test build, trigger the crash deliberately, relaunch as instructed and allow report delivery.
Do not ship a public crash button. If collection is controlled by consent or an application setting, test both enabled and disabled behavior instead of bypassing that logic to make the dashboard populate.
Check optimized-release readability
For an R8 release, confirm mapping upload and inspect a test crash from that exact build. Native crashes require the appropriate native integration and symbols; Java mapping does not cover arbitrary native frames.
| Observation | Next check |
|---|---|
| No report | Collection, initialization, network and app identity |
| Report in another app | Variant configuration |
| Obfuscated frames | Matching mapping upload |
| Native addresses only | Native symbol setup |
Keep evidence with the release
Record the test build identifier and report confirmation. APKLint's build and crash tools can support configuration and trace review, but they cannot prove that Firebase received a report. That last check must happen in the intended project's Crashlytics data.
Sources and further reading
- Firebase: Get started with Crashlytics on Android
- Firebase: Test your Crashlytics implementation
- Firebase: Android SDK release notes
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
