Error triage

The Errors page groups your app's errors so that each bug appears once, and lets you track each group until it's fixed. To open it, click Errors in the sidebar.

How Vexo groups errors

Errors with the same name, the same message, and the same top stack frame form one group. Vexo ignores numbers, hexadecimal values, and quoted text in the message, so Timeout after 3000ms and Timeout after 5000ms are one group.

Find an error

The list shows the error groups seen in the date range that you choose at the top of the page, most recently seen first. Use the Version, OS, and Country filters to narrow it, the status buttons to show All, Open, Regressed, Resolved, or Ignored groups, and Filter by assignee to show the groups assigned to a person or Unassigned ones.

Each row shows:

  • The error's message and name, when it was last seen, and the app versions that it appeared in.
  • How many times it happened, split into crashes and handled errors.
  • The share of users who hit it.

The list shows the 50 most recently seen groups. To find an older group, shorten the date range.

Investigate a group

Click a row to open the group's page. It shows:

  • Status and Assignee, and counts of occurrences, devices, crashes, handled errors, and fatal errors.
  • Latest stack trace: the newest occurrence, with the app version that it happened on. Click Watch replay to open the session replay at the moment of the error, or Go to session to see the session's events.
  • How many occurrences followed a tap, within 3 seconds.
  • Sessions with this error: up to 50 sessions, each with when it last hit the error.
  • Occurrences over time: a daily chart.

In the replay, the Network and Console tabs show the requests and console messages from that session. See Session Replays & Heatmaps.

Triage a group

Only the app's owner can change a group's status or assignee. Changes save as soon as you make them.

  • Open: the status of every new group.
  • Resolved: the bug is fixed. If the error happens again after you resolve it, in any app version, the group shows Regressed, along with the version that you resolved it in and the version where it came back. To clear Regressed, resolve the group again.
  • Ignored: a label for errors that you don't plan to fix. Ignored groups still appear under All, and still count toward crash-free sessions and alerts.

In Assignee, choose the owner or a member of the app's team. The app's audit log records each assignment.

Source maps

Release builds minify your JavaScript, so their stack traces point at the bundle, for example at t (index.android.bundle:1:452103). When you upload a release's source map, the Latest stack trace shows your original function names, files, and lines instead. The stack trace is marked Symbolicated when Vexo rewrote at least one frame, and Minified otherwise. If Vexo has no map for the release, the page says so.

To upload maps, you need vexo-analytics 1.11.0 or later, which includes the vexo-upload-sourcemaps command.

Upload a source map

  1. Build your release, and keep the source map that the build writes. For a Hermes build, use the map from the native release build, which maps the Hermes bytecode back to your code. To turn on source maps for a release build, see Debugging release builds in the React Native docs.
  2. Upload the map for each platform. For example, in your release pipeline:
npx vexo-upload-sourcemaps \
  --platform android \
  --sourcemap path/to/index.android.bundle.map \
  --app-version 1.4.0 \
  --api-key "$VEXO_API_KEY"

When the upload works, the command prints Uploaded path/to/index.android.bundle.map (<size> bytes) -> android 1.4.0 dist=embedded.

OptionValue
--platformRequired. ios or android.
--sourcemapRequired. The path to the source map.
--app-versionThe app version of the build: versionName on Android, or CFBundleShortVersionString on iOS. If you leave it out, the command uses expo.version from app.json or version from package.json, which might not match the build.
--api-keyRequired. The app's API key, the same key that you pass to vexo(). You can set the VEXO_API_KEY environment variable instead.
--distFor an over-the-air update from expo-updates, the ID of that platform's update. Defaults to embedded, for the code built into the app.

How Vexo matches a map

Vexo matches each error to the map with the same platform, the same app version, and the same update ID that the SDK reports for the device. Errors from the code built into the app match embedded.

If an over-the-air update has no map of its own, Vexo uses the build's embedded map, which no longer matches the update's code and can point at the wrong lines. Upload a map for each update, with --dist.

Vexo symbolicates a stack trace when you view it, so a map also works for errors that happened before you uploaded it. If someone viewed an error shortly before you uploaded its map, the error can show Minified until 30 minutes go by without anyone viewing it.

Uploading a map for the same platform, app version, and update again replaces the earlier map.

Limits

  • A map can be up to 64 MB, uncompressed.
  • Vexo symbolicates iOS and Android errors. It doesn't symbolicate web errors.
  • Index maps, which contain sections, aren't supported.
  • Vexo doesn't check a map when you upload it. If errors still show Minified, check that the platform, app version, and update ID match the build.
  • If the upload fails with Too many source map uploads in progress, retry it.

Crashes and handled errors

A crash is an error that your app didn't handle: an error that reached the top of the app, or one that you report with trackError(err, { handled: false }). Crash-free sessions and crash-free users count sessions and users without a crash. Errors that you report with trackError(err) are handled, and don't count against them. See Error reporting.

Vexo's SDK reports JavaScript errors. It doesn't capture native crashes, but you can import them from Firebase Crashlytics. See Crashlytics. When the JavaScript thread stops responding for 5 seconds or more, the SDK records it in the session's timeline, not on the Errors page.

Get notified

Vexo doesn't notify you about new or regressed groups. To hear about error spikes and crash-free drops, turn on Error spike, Crash-free sessions drop, Crash-free rate anomaly, or Error rate anomaly in Alerts. To file a Jira issue from the replay of an error, see Jira.