Distribute and grow
Distribute and grow

Crash analytics dashboard

Updated: Sep 30, 2024
The crash analytics dashboard offers in-depth insights into crash frequencies and types, to help you facilitate the debugging of Quest apps. To view the crash analytics dashboard, take the following steps:
  1. Open your browser and navigate to the Developer Dashboard⁠.
  2. Choose your app.
  3. From the left-side navigation click Analytics.
  4. From the expanded left-side menu, click Crash.

Key features of the dashboard

  • Data Aggregation: View aggregated data on unique crash events for up to 90 days.
  • Filtering Options: Filter crash data by crash type, device model, Meta Horizon OS version, app version, and date range.
  • Crash Types: Crashes are categorized into Native & Java crashes, Out of Memory crashes, and App Not Responsive crashes.
  • Crash Reasons: Groups related Native & Java crashes and App Not Responsive crashes if they share a common root cause.

Crash types

Currently, we exclude sideloaded app crashes, except for Out of Memory crashes. The following types of crashes are tracked and reported in this dashboard:
  • Native & Java: These crashes stem from errors within the app or system code and may cause the app to close unexpectedly.
  • App Not Responsive: If the UI thread of an Android app is blocked for an extended period, it triggers an Application Not Responding (ANR) error. Should this result in the app shutting down, the ANR will be documented in the crash reports. For a general procedure on detecting and investigating an ANR, visit the Android developer page on ANRs⁠.
  • Low Memory Kill: These crashes occur when the Android low memory killer daemon (lmkd)⁠ terminates an app process. We include LMKs only if an app is killed by lmkd while in the foreground and consuming more memory than the device SLA.

Using the time series chart

The Time Series chart helps you analyze crash data over time. You can:
  1. Choose one of three metrics to display.
  2. Break down the metrics by crash type, device model, Meta Horizon OS version, app version, and crash reason.
  3. Select for daily or hourly data granularity. Note that hourly data is retained for a shorter period.
Screenshot of the main page and the time series chart. Crash reason table not shown.

Detailed crash information

Selecting a crash reason below the chart opens a new view showing:
  • Metrics specific to the selected crash reason.
  • Sampled stack traces, available only for Java & Native crashes.
Details page and beginning of stack trace

Symbolicated stack traces

Uploading debug symbol files for your app enables symbolicated stack traces, enhancing crash cause analysis. For instructions on uploading these files, see Upload Quest Debug Files for Crash Analytics. Without debug symbol files, or if the crash hasn’t recurred after uploading, stack traces will only show memory addresses.
Did you find this page helpful?
Nav Logo
Virtual reality / Meta Horizon
Virtual reality / Meta Horizon
Virtual reality / Meta Horizon
English (US)
© 2026 Meta