We are excited to announce the launch of Crash Analytics, one of the most requested features from our developer community. Our new crash reporting tools show technical details on crashes experienced by users, broken down by app version, time, and headset (Quest and Quest 2). This dashboard of information will help you identify, prioritize and fix stability issues affecting your application. Starting today, Crash Analytics is available to all Quest developers on the Developer Dashboard.
The Crash Analytics dashboard is available on the Developer Dashboard under an application’s Analytics section in a new tab labeled “Crash”. The overview page was designed to give you actionable information at a glance. Total number of crash events and active/affected users are shown at the top of the page and can be filtered by device model, app version, and date range.
You can quickly drill down using these filters to focus on a specific period. The line graph can help you quickly spot trends and identify when stability issues spiked or improved. The table below the graph further expands on the crashes identified for this period of time. You can sort by Affected Users or Crash Events, and then drill into a specific crash type to get more information.
“Oculus’s new Crash Analytics dashboard has been invaluable for quantifying the most important and frequent crashes on Echo VR. For a live game it's critical to find the bugs that were missed by QA but affect the user base. The easy-to-use interface has allowed our engineers to stay on top of live bugs and quickly reduce the crash rate of our game.”
-David Neubelt, Lead Engineer, Ready at Dawn
Clicking on a specific Crash Reason opens another view with more detailed information about that specific issue. This information can help you isolate a crash to a specific version or device. Understanding which subset of your users are affected can help you quickly identify and fix the crash.
Previously, Quest developers had limited information to debug crashes reported by users. We now provide stack traces so you can quickly debug and fix crashes. These provide additional information and context on why a crash occurred and what happened leading up to it. We highly encourage all developers to upload their debug symbols so you can get access to full symbolicated stack traces.
You can upload debug symbols with your APK via the Oculus Platform Command Line Utility (CLI) or directly from our v25 Unity and Unreal engine integrations. For developers with existing applications, you can use the CLI to attach debug symbol files to a Quest app previously uploaded to a release channel. See our Upload Quest Debug Files for Crash Analytics documentation.
The Oculus Platform Tool in Unity will have a new Debug Symbols Directory field. The Oculus Platform tool, by default, points to the debug symbol directory path for the builds compiled using the IL2CPP backend script. You can select the path for builds compiled using the Mono script, or you can clear the path if you do not want to upload the debug symbols file.
The Oculus Platform Tool in UE4 also provides a way to upload the symbols natively through the Symbol Directory Path field, which is prepopulated to the standard UE4 symbol path for your project. If it fails, point it at the directory containing the symbolicated libUE4.so (it should be more than 1Gb).
We’re excited to launch Crash Analytics today and provide you with more data and information to improve your applications. We look forward to learning more about how our developers use Crash Analytics and improving the product over time. We welcome your feedback!