Crash reporting
See the errors your users hit — grouped into issues with the stack, the Sovaria calls that led up to them, the device and the release — from one line of SDK code.
Add one line to your app and every uncaught error is reported to your project, in browsers and React Native. Reports are grouped into issues — the same bug is one issue across releases, line changes and ids — and each keeps how often it happened, how many users it hit, when it started, the latest release, and the last 50 reports in full.
import { SovariaSDK } from '@sovaria/sdk'
const sov = new SovariaSDK({ projectUrl: 'https://<ref>.sovaria.in', anonKey: '<anon key>' })
sov.crashes.install({ release: '2.4.1', environment: 'production' })
// Errors you catch yourself
try {
await checkout(cart)
} catch (e) {
sov.crashes.capture(e, { tags: { step: 'pay' }, extra: { items: cart.length } })
}
// Your own breadcrumbs, next to the Sovaria calls the SDK records for you
sov.crashes.addBreadcrumb({ category: 'ui', message: 'tapped Pay' })What a report contains
| Field | Where it comes from |
|---|---|
| Error type, message and stack | The error; the top frames (without line numbers or query strings) group reports into issues. Pass fingerprint to group your own way. |
| Breadcrumbs | The last 50: every Sovaria call the SDK made (method, path, status — no bodies or tokens) and your own addBreadcrumb. |
| User | The signed-in app user, taken by the server from the request's token (an app can't claim another user). Anonymous otherwise. |
| Release, environment, platform, device, page | What you pass to install, plus browser or React Native details. |
| Tags and extra | Whatever you pass to capture; fields named like passwords, tokens, keys or cookies are removed before storage. |
Working with issues
- In the console, Crashes lists open issues with events, users and last seen; open one for the stack, the calls before it, the context and recent reports.
- Resolve an issue when the fix ships: if it happens again it reopens on its own, so regressions don't hide. Ignore hides one you won't fix.
- Sovariq can read crashes for you ("why does checkout crash?") — it sees the same issues and reports, and proposes a fix.
Plans and limits
| Free | Pro | Ultra | Team | Enterprise | |
|---|---|---|---|---|---|
| Crash reports per month (per project) | 5,000 | 100,000 | 500,000 | 2,000,000 | 10,000,000 |
| Days issues are kept | 7 days | 30 days | 90 days | 90 days | 365 days |
Past the monthly limit reports are dropped and counted (the Crashes page shows how many). The SDK also drops duplicates within a second and sends at most 30 a minute, so a crash loop can't use up the month.
Something unclear or missing on this page?Tell us