Crash reporting with Trace

Published at 2021-02-11

Japanese translation unavailable

This page has not been translated into Japanese yet - we apologise for the inconvenience! If you’re interested in helping us out, feel free to translate any article in the jp folder of the DevCenter repository and open a PR!

このページは日本語への翻訳がまだ完了しておりません。ご不便をおかけして申し訳ございません! もしお手伝いできる方がいらっしゃれば、ご自由にjpフォルダの記事を日本語に訳していただき、PRを開いてください

Trace’s crash reporting feature helps you understand and prioritize the issues within your app. Trace provides crash reporting by default: all you need to do to make it work is to install the Trace SDK to your app.

Within Trace itself, the Crashes page shows all crashes, the number of affected users, the affected app versions, and the last time these crashes were observed.

Trace will group your crash reports based on the exception details, so that you can clearly see the different issues being reported by your app. For each issue, we report the number of users that are affected by this problem, so that you can prioritize the critical issues.

Finding a crash report

To check a crash report:

  1. Go to the Crashes page in Trace.
    The Crashes page in Trace
  2. Optionally, filter the reports by status (open or closed) or date range to find the relevant crashes easier.
  3. Click on the crash report you need.

Clicking on a crash report takes you to the crash details view which displays all the relevant information about a crash.

The crash details view

The crash details shows you plenty of information about any given crash:

The main body of the page shows the details of an individual instance of a crash report. You can inspect each instance by paging through them using the navigation buttons at the top.

The crash details view in Trace

The provided details include: