Enable the correct package
The DebugView guide documents the Android debug property:
adb shell setprop debug.firebase.analytics.app com.example.app
Replace the package with the installed variant's real application ID. A .debug suffix changes the value you need; the project display name is not the package name.
Trigger a small, identifiable event sequence
Open the app, perform one known action and inspect the expected Firebase project. Use stable event names and parameters that describe the action without exposing personal information.
Check event spelling, parameter types and repeated firing. A button that emits three events for one tap can look like successful instrumentation while corrupting the metric you intend to measure.
Diagnose a missing stream
| Check | Why it matters |
|---|---|
| Package property | Debug mode targets one installed identity |
| Firebase project/app | Configuration may point to staging |
| Analytics collection state | Consent or settings may disable collection |
| Network and initialization | Events need a functioning delivery path |
| Event implementation | The expected code path may not run |
Do not turn off privacy controls permanently just to make a test event appear. Test the enabled path and the denied path independently.
End the debug session
Disable the property when finished:
adb shell setprop debug.firebase.analytics.app .none.
This matters on shared test devices where a later tester could otherwise interpret debug behavior as normal production behavior.
Separate event validation from business reporting
A visible DebugView event confirms a narrow path from this test device to this Firebase app. It does not establish Google Ads import, attribution windows, revenue values or production aggregate counts.
APKLint's Firebase Config Scanner can help identify the app's configuration and its package relationship. It cannot read your analytics stream. Keep a redacted event specification and test record, then verify downstream reporting separately where that is part of the product requirement.
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
