Dartastic Help

From your first sign-in to answers about your app in production.

These pages show Cloud's URLs. Sign in on Hosted and they show your server's.

The Crashes list

The Crashes list groups the exceptions your app did not catch into issues, most occurrences first, with the builds and people each one reaches.

Open it from Dashboards in the Observatory: under Lists, choose Crashes. The button in its header, Every exception, switches to the Issues list over the same range and build, and All dashboards goes back.

[TODO: screenshot of the Crashes list over the last 24 hours, every filter All: the header with its counts and Every exception, the Build menu, and three issues with their top frames, trends and Open trace]

What counts

A crash is an exception the app did not catch. That is the one thing "crash" means in the Observatory: this list counts crashes. The session panels on the dashboards, such as Crash-free sessions and Crashed sessions, count sessions, not crashes.

Exceptions with the same issue id are one issue. An exception without one is grouped with others of the same type and top frame.

Build and the time range

  • Build narrows the list to one build. Its menu lists the builds the list names, the build with the most crashes first.
  • The time range: Last hour, Last 6 hours, Last 12 hours, Last 24 hours (the default), Last 7 days, Last 14 days or Custom. A custom range can span up to 14 days; a link with a longer one shows its last 14 days.
  • The line under the title sums it up, as in 12 crashes in 3 issues · last 24 hours, and names the build when one is picked.

Each issue

  • The type and top frame: the exception's type in bold, then the top frame of its stack, from the symbolized stack when there is one. When there is not, the chip not symbolized says so; an exception with no stack shows no stack.
  • The message under it.
  • Builds, first and last: its first two builds, each with its count, then how many more (and 3 more builds), and when it was first and last seen in the range.
  • The trend: small bars across the range, each one the issue's occurrences in that stretch of time.
  • Occurrences, Users and Sessions: how many times it happened, and how many users and sessions it reached.
  • Open trace opens its newest occurrence's trace at the span that recorded it. When that occurrence has no trace, the issue shows no trace.

How many show

The list shows up to 50 issues. Its heading says how many of how many, as in Showing 50 of 212 issues · most occurrences first, or Showing all 12 when every one fits.

The top bar's Ask Dartastic AI asks with this list, its range and its build in view.

Nothing found, or no access

  • No crash last 24 hours (or in the range you set) means nothing the app reported matched. A longer range may find older ones.
  • We couldn't load the crashes comes with a retry; a shorter range reads faster.
  • Reading the list needs the Observatory Viewer role in your organization. An Owner or Admin can grant it on the Members page.