DebugView lets you to see the raw event data logged by your app on
development devices in near real-time. This is very useful for validation
purposes during the instrumentation phase of development and can help you
discover errors and mistakes in your Analytics implementation and confirm
that all events and user properties are logged correctly.
## Enable debug mode
Generally, events logged by your app are batched together over the period of
approximately one hour and uploaded together. This approach conserves the
battery on end users' devices and reduces network data usage. However, for the
purposes of validating your Analytics implementation (and, in order to
view your Analytics in the DebugView report), you can enable debug mode
on your development device to upload events with a minimal delay.
### iOS+
To enable Analytics debug mode on your development device, specify the
following command line argument in Xcode:
-FIRDebugEnabled
This behavior persists until you explicitly disable debug mode by specifying
the following command line argument:
-FIRDebugDisabled
You can add these arguments by editing your project's scheme and adding a
new entry to "Arguments Passed On Launch".
### Android
To enable Analytics debug mode on an Android device,
execute the following commands:
```
adb shell setprop debug.firebase.analytics.app PACKAGE_NAME
```
This behavior persists until you explicitly disable debug mode by executing
the following command:
```
adb shell setprop debug.firebase.analytics.app .none.
```
### Web
To enable Analytics debug mode in your browser, install the
[Google Analytics Debugger](https://chrome.google.com/webstore/detail/google-analytics-debugger/jnkmfdileelhofjcijamephohjechhna)
Chrome extension.
Once installed, enable the extension and refresh the page. From that point
on, the extension will log events in your app in debug mode.
You can view events logged in the DebugView in the Firebase console.
> [!NOTE]
> **Note:** Events logged while in debug mode are intended for real-time validation during development. These events are included in your daily BigQuery export by default. To prevent developer and test traffic from being processed and appearing in your reports or BigQuery exports, you should configure a developer traffic data filter within your Analytics property. Learn more about excluding developer traffic using [Data Filters](https://support.google.com/analytics/answer/13296662?sjid=2496304241652799595-NC).
### View `error` events
Both automatically logged `error` events (which indicate issues with event or
user property logging) and other events that include a `firebase_error`
parameter appear in the DebugView report.
Note that while `error` events appear directly in the stream, for other events
that include a `firebase_error` parameter, DebugView does not display a special
error indicator in the main event stream. You must click the event
to view the `firebase_error` parameter in the parameters list.
To help debug Analytics implementation errors, check the device console
logs for messages from the Firebase Analytics SDK, which often provide details
on why an event or parameter was rejected.
## Report on event data
1. Make sure that you've enabled debug mode on your development devices as
described in the previous section of this guide.
2. In the Firebase console, go to **Analytics** \>
[**DebugView**](https://console.firebase.google.com/project/_/analytics/debugview).
3. Start interacting with your app to see your app's events being logged in the
DebugView report within the Firebase console.
The Seconds stream (the middle column) shows the events which have been logged
in the last 60 seconds. The Minutes stream (the left column) shows a series of
archives of events over the last 30 minutes. And the right column shows the
Top Events logged in the 30-minute period as well as the Current User Properties
for the selected development device.
### Seconds stream
By default, you will see a list of events logged in the last 60 seconds. Each
event displays a timestamp that corresponds to the time of its logging on the
development device. You can click an event to see a list of the parameters
that were associated with that event.
As user property values change during the course of app usage, you will see an
entry for that change.
### Minutes stream
This stream shows a series of circles which each correspond to a minute of time
over the last 30 minutes. The number in the circle indicates the count of
events received in that minute. Clicking on one of these circles will populate
the Seconds stream with events which were logged during that minute of time.
This effectively lets you examine the events logged over the last 30
minutes in fine-grained detail.
### Top events and Current User Properties
The Top Events table shows the top events which were logged during the 30-minute
period. And the Current User Properties table shows the latest state of the set
of User Properties for the selected development device.
### Device selector
Since many different development devices can have debug mode enabled, you can
use the Device selector to choose the specific device on which the DebugView
report will focus. This allows multiple developers to focus on their own
instrumentation and validation efforts without impacting one another.
