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.
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.
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 list shows the 50 most recently seen groups. To find an older group, shorten the date range.
Click a row to open the group's page. It shows:
In the replay, the Network and Console tabs show the requests and console messages from that session. See Session Replays & Heatmaps.
Only the app's owner can change a group's status or assignee. Changes save as soon as you make them.
In Assignee, choose the owner or a member of the app's team. The app's audit log records each assignment.
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.
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.
| Option | Value |
|---|---|
--platform | Required. ios or android. |
--sourcemap | Required. The path to the source map. |
--app-version | The 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-key | Required. The app's API key, the same key that you pass to vexo(). You can set the VEXO_API_KEY environment variable instead. |
--dist | For 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. |
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.
sections, aren't supported.Too many source map uploads in progress, retry it.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.
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.