Skip to content
ErrorDock

React Native SDK

JavaScript errors, sessions and explicit screen tracking for React Native.

Release candidate: @errordock/react-native is published on npm at 0.1.0-rc.2, with @errordock/core. Pin that version when you install, because npm's latest tag still points at the older rc.1.

The SDK captures uncaught JavaScript errors through ErrorUtils and reports sessions, screens and feature usage. It captures JavaScript crashes only: native crash capture is not provided by this JavaScript integration.

Install

npm install @errordock/core@0.1.0-rc.2 @errordock/react-native@0.1.0-rc.2 @react-native-async-storage/async-storage

Configure

Use an application key (ed_app_) in a distributed app. Add persistent storage to retain the install identity and offline queue between launches, and register your root component through wrap:

import { AppRegistry } from "react-native";
import AsyncStorage from "@react-native-async-storage/async-storage";
import { init, wrap } from "@errordock/react-native";
import App from "./App";
import { name as appName } from "./app.json";

init({
  apiKey: "ed_app_...",
  endpoint: "https://api.errordock.com",
  environment: "production",
  release: "2.8.4",
  storage: AsyncStorage,
});

AppRegistry.registerComponent(appName, () => wrap(App));
// Expo: registerRootComponent(wrap(App));

Offline and crashes

Events wait in a persistent queue while the device is offline. A crash is kept and sent on the next launch, for up to 30 days. Fetch and XHR tracing is available and off unless you switch it on.

Identity

With persistent storage the SDK keeps an anonymous install id, so a device is counted before anyone signs in. Set your own user id to count a person across devices; see Users and identity.

Source maps

Hermes stack traces resolve through the composed Hermes source map for the release. Upload it the same way as a browser map; see Releases. During the beta, source-map upload is enabled per organisation.

Last updated October 20, 2026