Observe
Crash Reporting
Automatically capture JavaScript errors, uncaught exceptions, and promise rejections. Every crash includes a full stack trace, user session context, breadcrumbs, and timeline position.
What You Get
Automatic Capture
The SDK intercepts JS errors and unhandled promise rejections without any manual instrumentation.
Full Stack Traces
Each error includes the complete JavaScript call stack with file names and line numbers.
Breadcrumbs
The last user actions before the crash — navigation, taps, network requests — are captured as breadcrumbs.
Manual Reporting
Use reportError() to capture handled errors with custom context and metadata.
Real-Time Desktop Streaming
View crashes as they happen in the Desktop App’s Crashes panel.
Session Context
Every error is linked to the user session, device info, and app state at the time of occurrence.
FAQ
What types of errors does WhatzBug catch?
The SDK automatically captures JavaScript errors, uncaught exceptions, and unhandled promise rejections. Errors are enriched with stack traces, timestamps, session context, and breadcrumbs.
Does crash reporting work without the Desktop App?
Yes. The SDK captures errors independently and can send them to the WhatzBug backend. The Desktop App provides real-time error streaming during development.
Can I report errors manually?
Yes. Use WhatzBug.reportError() to capture handled errors with custom context.