For React Native
ErrorDock for React Native.
Connect JavaScript failures to the screens, interactions and releases behind them. Persistent storage keeps the offline queue and install identity between launches. Native crash capture is outside this JavaScript integration.
An application journey
Capture JavaScript errors through ErrorUtils and name screen views explicitly. Connect those events to feature usage in the same project.
Release attribution
Set the release and environment during initialisation so errors can be connected to the version your users are running.
Keep events through a lost connection
Pass persistent storage to retain the offline queue across launches. Use an application key in the distributed binary; keep server keys on your server.
Related
- ErrorDock for React. Error boundaries, component stacks and feature usage tracking for React applications, from one SDK.
- Find the failure. Keep the context. Group exceptions into issues, inspect stack traces and breadcrumbs, and understand which users and releases are affected.
- See what changed. Catch what came back. Attach release information to telemetry, compare application versions and connect regressions to the code your team shipped.
Bring your application into focus.
Tell us about your stack. We will help define the right beta setup for your first project.