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.
Validate one event against a written contract
For a document preview feature, define an illustrative custom event named preview_open with a controlled origin value such as library or search. Do not include the document's title, contents or account identifier. State when the event should fire: once when the user actually opens the preview, rather than every time the screen recomposes or returns from a temporary configuration change.
Enable debug collection for the exact installed package and perform one action. In Firebase DebugView, inspect the event name, parameter type and count. Repeat the action from the second origin and compare the expected controlled value. A visible event with the wrong parameter type is a contract failure even though delivery succeeded.
Look for lifecycle-driven duplication
Open the preview, rotate or recreate the screen where supported, return to the previous screen and open it again. Record which transitions are intended to create a new event. If a single opening produces multiple events, inspect lifecycle listeners and callbacks before treating the larger count as more engagement. Keep the test sequence small enough that each observed event can be matched to a deliberate action.
Test the application's collection-disabled state separately. The expected observation should follow the implemented consent or preference design, not a temporary debug bypass. A missing event in that state may be correct. When a permitted event is missing, compare package identity, Firebase destination and code-path execution before changing event names or adding duplicate logging calls.
Disable the debug property after testing and document that cleanup on a shared device. Keep a redacted event contract and the tested build identifier with the instrumentation change. Validate downstream business reporting separately when required: DebugView does not prove attribution, advertising imports, conversion definitions or revenue accounting. A precise event test establishes that one controlled client action produced the intended analytics payload, and its value comes from that narrow, reproducible scope.
Sources and further reading
Reference review: 29 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
