Skip to main content

​
What it does

Error Tracking captures crashes and exceptions from your app and turns them into actionable issues in your dashboard — without you having to build your own crash-reporting pipeline.
  • Automatic capture. Once the SDK is initialized, uncaught errors are reported without any extra code on your part.
  • Manual reporting. Catch an exception yourself and send it with extra context — a bugType, a bugSeverity, and arbitrary metadata (user ID, the action being performed, anything else useful for debugging).
  • Device and app context on every report. Device model, OS/version, architecture, timezone, country, and your app’s version/build number are attached automatically — you don’t have to collect and send them yourself.
  • AI-assisted summaries. Bug details in the dashboard include an AI summary panel that helps you understand what went wrong faster.
  • Assign and discuss. Assign a bug to a teammate and comment on it directly in the dashboard as you work through a fix.

​
Classification

Reports carry a bugType (e.g. crash, networkError, uiBug, performance) and a bugSeverity (critical down to low) so you can triage what matters first. See your framework’s guide for the full list of values.

​
Source maps

Production web builds are minified, so a browser stack trace points at positions in bundled chunks, like onConnMessage@https://app.com/chunk-Cr8GYWvZ.js:10:14780, instead of your code. Upload your build’s source maps with the Lerix CLI and new errors show the original file, line and function (for example src/app/chat/chat.page.ts:142) with the surrounding code. The maps are uploaded privately and removed from your build output before you deploy, so your source is never served publicly. The AI assistant, GitHub issues and the MCP server all see the readable stack too.

Angular

Hidden source maps in angular.json, then upload.

React

Source maps with Vite or Create React App, then upload.

Next.js

productionBrowserSourceMaps, then upload.

Flutter

flutter build web --source-maps, then upload.
Backend SDKs need no upload. NestJS reads the .js.map files that nest build writes (see TypeScript file and line numbers), and ASP.NET Core reads the debug info in your build (see File and line numbers).

​
Get started

Flutter

Set up automatic and manual error reporting in a Flutter app.

iOS (Swift)

Automatic crash capture and manual error reporting in a native iOS app.

NestJS (backend)

Automatic reporting of unhandled exceptions in a NestJS API, with request context.
More framework guides are on the way — see the Getting Started page for current platform availability.