Yes. Crash reporting shares one identity layer with analytics and session replay, so a crash can be viewed alongside the events and the session that preceded it.
Features · Bugs & Crashes
Bugs & Crashes
Catch crashes and errors with symbolicated stack traces, tied to the events and session that preceded them — on the same SDK that captures the surrounding behavior.
Read the crashes & errors docs Errors & crashes on the web Talk to the team
Capabilities
What bugs & crashes gives you
Crash reporting and error monitoring with symbolicated stack traces, on React Native and in the browser.
The trail before the error, not just the stack
Breadcrumbs turn "it threw here" into "here is what the user did first." Console output is captured automatically, and the ring is bounded — 50 entries by default, 200 maximum — so adding your own liberally stays safe.
Errors you throw, and the ones you never see
Unhandled exceptions and unhandled promise rejections are captured without wiring, and anything you catch yourself can be reported explicitly with its own scope, tags and context.
From the error to the session that caused it
Errors share one identity layer and event schema with replay and analytics, so a crash links to the replay of the session that produced it and to what the user did before it — no correlating ids across tools.
The SDK
Built as one lightweight SDK, not five disconnected tools.
One install brings the whole platform online, with the plumbing — queueing, batching, retries, and masking — handled for you.
- One installation
- OTA bundle updates
- One identity layer
- One event schema
- Offline queueing
- Batching & retrying
- Privacy controls
- Masking by default
- iOS · Android · RN
- Server-side APIs
- Webhooks
- Data export
App.tsx
FAQ
Bugs & Crashes — common questions
Install once. Understand everything.
See every journey. Fix every issue. Grow every user.
One SDK, one timeline, and one dashboard for marketing, product, and engineering.