---
title: "React Error Boundary"
description: "Learn how the React Native SDK exports an error boundary component that leverages React component APIs to catch rendering errors and display fallback UIs."
url: https://docs.sentry.io/platforms/react-native/integrations/error-boundary/
---

# React Error Boundary | Sentry for React Native

The React Native SDK exports an error boundary component that uses [React component APIs](https://react.dev/reference/react/Component#catching-rendering-errors-with-an-error-boundary) to automatically catch and send JavaScript errors from inside a React component tree to Sentry, and render a fallback UI.

##### Render errors only

React error boundaries **only catch errors during rendering, in lifecycle methods, and in constructors**. They do **not** catch errors in event handlers, asynchronous code (`setTimeout`, `Promise`), or native errors. For a fallback UI that covers those cases too, use [`Sentry.GlobalErrorBoundary`](https://docs.sentry.io/platforms/react-native/integrations/error-boundary.md#showing-a-fallback-ui-for-fatal-errors).

##### Recommended on Android

On Android, some render-time errors (such as `TypeError` from calling a non-function) can bypass the global error handler entirely. Wrapping your app or error-prone components with `ErrorBoundary` ensures these errors are reliably captured and reported to Sentry.

## [Prerequisites](https://docs.sentry.io/platforms/react-native/integrations/error-boundary.md#prerequisites)

To use the Error Boundary component, you need to have the React Native SDK [installed and configured for error monitoring](https://docs.sentry.io/platforms/react-native.md).

## [Use `Sentry.ErrorBoundary`](https://docs.sentry.io/platforms/react-native/integrations/error-boundary.md#use-sentryerrorboundary)

```javascript
import React from "react";
import { Text } from "react-native";
import * as Sentry from "@sentry/react-native";

<Sentry.ErrorBoundary fallback={<Text>An error has occurred</Text>}>
  <Example />
</Sentry.ErrorBoundary>;
```

The Sentry Error Boundary is also available as a higher-order component.

```javascript
import React from "react";
import { Text } from "react-native";
import * as Sentry from "@sentry/react-native";

Sentry.withErrorBoundary(Example, {
  fallback: <Text>An error has occurred</Text>,
});
```

##### Note

In development mode, React will rethrow errors caught within an error boundary to the global error handler. This will result in Sentry only reporting an error from the global error handler, but not from the error boundary itself. We recommend testing the error boundary with a production build of React.

In the example below, when the `<Example />` component hits an error, the `<Sentry.ErrorBoundary>` component will send data about that error and the component tree to Sentry, open a user feedback dialog, and render a fallback UI.

```javascript
import React from "react";
import { Text } from "react-native";
import * as Sentry from "@sentry/react-native";

import { Example } from "../example";

function FallbackComponent() {
  return <Text>An error has occurred</Text>;
}

const myFallback = <FallbackComponent />;
// Alternatively:
// const myFallback = () => <FallbackComponent />;

class App extends React.Component {
  render() {
    return (
      <Sentry.ErrorBoundary fallback={myFallback} showDialog>
        <Example />
      </Sentry.ErrorBoundary>
    );
  }
}

export default App;
```

##### Note

By default, React [logs all errors to the console](https://github.com/facebook/react/blob/493f72b0a7111b601c16b8ad8bc2649d82c184a0/packages/react-reconciler/src/ReactFiberErrorLogger.js#L85), even if you're using a React error boundary. If you're using the `CaptureConsole` integration, Sentry will capture the error there and not through the error boundary.

## [Linked Errors](https://docs.sentry.io/platforms/react-native/integrations/error-boundary.md#linked-errors)

In [React v17 and above](https://reactjs.org/blog/2020/08/10/react-v17-rc.html#native-component-stacks), the SDK will automatically parse the [error boundary](https://react.dev/reference/react/Component#componentdidcatch-parameters) `componentStack` and attach the full stacktrace to the event via `error.cause`. This requires the `nativeLinkedErrorsIntegration` to be enabled. (It's enabled by default.) To get the full source context, we recommend setting up [source maps](https://docs.sentry.io/platforms/react-native/sourcemaps.md) for your project.

## [Handling Non-Render Errors](https://docs.sentry.io/platforms/react-native/integrations/error-boundary.md#handling-non-render-errors)

Errors in event handlers, `async` functions, `setTimeout`, and other non-render code won't be caught by `ErrorBoundary`. This is a [React limitation](https://react.dev/reference/react/Component#catching-rendering-errors-with-an-error-boundary), not specific to Sentry.

Sentry's [`reactNativeErrorHandlersIntegration`](https://docs.sentry.io/platforms/react-native/integrations/default.md#reactnativeerrorhandlersintegration) (enabled by default) **automatically reports** these errors to Sentry — you don't need to do anything extra for error reporting. For a fallback UI on fatal non-render errors, use [`Sentry.GlobalErrorBoundary`](https://docs.sentry.io/platforms/react-native/integrations/error-boundary.md#showing-a-fallback-ui-for-fatal-errors).

### [Component-Level Error Handling](https://docs.sentry.io/platforms/react-native/integrations/error-boundary.md#component-level-error-handling)

For errors in event handlers or async code within a specific component, use `try`/`catch` with local state:

```javascript
import React, { useState } from "react";
import { Button, Text } from "react-native";
import * as Sentry from "@sentry/react-native";

function MyComponent() {
  const [error, setError] = useState(null);

  const handlePress = async () => {
    try {
      await riskyOperation();
    } catch (e) {
      Sentry.captureException(e);
      setError(e);
    }
  };

  if (error) {
    return (
      <>
        <Text>Something went wrong.</Text>
        <Button onPress={() => setError(null)} title="Retry" />
      </>
    );
  }

  return <Button onPress={handlePress} title="Do thing" />;
}
```

### [Showing a Fallback UI for Fatal Errors](https://docs.sentry.io/platforms/react-native/integrations/error-boundary.md#showing-a-fallback-ui-for-fatal-errors)

To show a fallback UI for fatal JavaScript errors that are thrown **outside** the React render tree — event handlers, `setTimeout`, async code, and errors routed through `ErrorUtils` — wrap your app in `Sentry.GlobalErrorBoundary`:

```javascript
import React from "react";
import { Button, Text, View } from "react-native";
import * as Sentry from "@sentry/react-native";

function App() {
  return (
    <Sentry.GlobalErrorBoundary
      fallback={({ error, eventId, resetError }) => (
        <View>
          <Text>Something went wrong.</Text>
          <Text>{error?.message}</Text>
          <Text>Event ID: {eventId}</Text>
          <Button onPress={resetError} title="Restart" />
        </View>
      )}
    >
      <RestOfYourApp />
    </Sentry.GlobalErrorBoundary>
  );
}
```

`GlobalErrorBoundary` is a superset of `ErrorBoundary`: it catches everything `ErrorBoundary` catches **and** fatal non-rendering errors routed through React Native's `ErrorUtils` global handler. The error is captured through Sentry's normal pipeline (with the correct `mechanism` and `fatal` level) before the fallback is rendered — no duplicate events, no need to call `Sentry.captureException` yourself.

In release builds, `GlobalErrorBoundary` takes over React Native's default fatal handler so the fallback can own the screen instead of the app being torn down. In development, LogBox still appears — the fallback renders alongside it.

#### [Opt-In Options](https://docs.sentry.io/platforms/react-native/integrations/error-boundary.md#opt-in-options)

By default, only fatal errors trigger the fallback. Two props extend coverage:

```javascript
<Sentry.GlobalErrorBoundary
  // Also render the fallback for non-fatal ErrorUtils errors
  includeNonFatalGlobalErrors
  // Also render the fallback for unhandled promise rejections
  includeUnhandledRejections
  fallback={/* ... */}
>
  <App />
</Sentry.GlobalErrorBoundary>
```

Most apps should leave both off: non-fatals are often recoverable, and unhandled rejections are frequently surfaced as toasts or inline errors rather than as a full-screen fallback.

#### [HOC Alternative](https://docs.sentry.io/platforms/react-native/integrations/error-boundary.md#hoc-alternative)

```javascript
import * as Sentry from "@sentry/react-native";

export default Sentry.withGlobalErrorBoundary(App, {
  fallback: ({ error, resetError }) => (
    <Fallback error={error} onRetry={resetError} />
  ),
});
```

##### Reset semantics

`resetError()` clears the fallback and remounts the children, but it does **not** restore JavaScript state that was corrupted by the error. Use `onReset` to navigate to a safe screen, reload data, or reset your state container.

#### [Migration From a Hand-Rolled `setGlobalHandler`](https://docs.sentry.io/platforms/react-native/integrations/error-boundary.md#migration-from-a-hand-rolled-setglobalhandler)

Before `GlobalErrorBoundary`, showing a fallback for non-render errors required overriding `ErrorUtils.setGlobalHandler`, bridging through `DeviceEventEmitter`, and combining with `ErrorBoundary`. This is **no longer recommended** — the manual approach bypasses Sentry's flush and fatal deduplication, risks running the app in a corrupted state, and is fragile across React Native versions.

```javascript
// ❌ Before: manual global handler + ErrorBoundary
const defaultHandler = global.ErrorUtils?.getGlobalHandler();
global.ErrorUtils?.setGlobalHandler((error, isFatal) => {
  DeviceEventEmitter.emit("GLOBAL_UNHANDLED_ERROR", error);
  if (__DEV__) defaultHandler?.(error, isFatal);
});
// ...plus a provider subscribing to the event and an ErrorBoundary

// ✅ After: one component
<Sentry.GlobalErrorBoundary fallback={/* ... */}>
  <App />
</Sentry.GlobalErrorBoundary>
```

If you previously disabled the `onerror` integration to avoid duplicate reports, re-enable it (or remove the `reactNativeErrorHandlersIntegration({ onerror: false })` override) — `GlobalErrorBoundary` relies on it for capture.

## [Options](https://docs.sentry.io/platforms/react-native/integrations/error-boundary.md#options)

The ErrorBoundary component exposes a variety of props that can be passed in for extra configuration. There aren't any required options, but we highly recommend setting a fallback component.

`fallback` (React.ReactNode or Function)

A React element to render when the error boundary catches an error. This can be an actual React element (for example, `<Fallback />`), or a function that returns a React element. If you provide a function, Sentry will call it with additional info and helpers (see example below).

`onError` (Function)

A function that gets called when the Error Boundary encounters an error. `onError` is useful if you want to propagate the error into a state management library like Redux, or if you want to check any side effects that could have occurred due to the error.

`onMount` (Function)

A function that gets called on ErrorBoundary `componentDidMount()`.

`onUnmount` (Function)

A function that gets called on ErrorBoundary `componentWillUnmount()`.

`beforeCapture` (Function)

A function that gets called before an error is sent to Sentry, allowing for extra tags or context to be added to the error.

### [`GlobalErrorBoundary`-Only Options](https://docs.sentry.io/platforms/react-native/integrations/error-boundary.md#globalerrorboundary-only-options)

`GlobalErrorBoundary` accepts every `ErrorBoundary` option above plus:

`includeNonFatalGlobalErrors` (boolean, default `false`)

Also render the fallback when a non-fatal error is reported through `ErrorUtils`. Off by default to match the semantics of React Native's native red-screen, which only appears for fatals.

`includeUnhandledRejections` (boolean, default `false`)

Also render the fallback when an unhandled promise rejection occurs. Off by default because many apps prefer to surface rejections as toasts or inline errors rather than as a full-screen fallback.

## [Examples](https://docs.sentry.io/platforms/react-native/integrations/error-boundary.md#examples)

### [Setting a Fallback Function (Render Props)](https://docs.sentry.io/platforms/react-native/integrations/error-boundary.md#setting-a-fallback-function-render-props)

Below, is an example where a fallback prop, using the [render props approach](https://react.dev/reference/react/cloneElement#passing-data-with-a-render-prop), is used to display a fallback UI on error. The fallback UI returns to a standard component state when reset using the `resetError()` API, provided by the component through render props.

```javascript
import React from "react";
import { Button, Text } from "react-native";
import * as Sentry from "@sentry/react-native";

class MyComponent extends React.Component {
  constructor(props) {
    super(props);
    this.state = {
      message: "This is my app",
    };
  }

  render() {
    return (
      <Sentry.ErrorBoundary
        fallback={({ error, componentStack, resetError }) => (
          <React.Fragment>
            <Text>You have encountered an error</Text>
            <Text>{error.toString()}</Text>
            <Text>{componentStack}</Text>
            <Button
              title="Click here to reset!"
              onPress={() => {
                this.setState({ message: "This is my app" });
                // When resetError() is called it will
                // remove the Fallback component and render
                // the Sentry ErrorBoundary's children
                // in their initial state
                resetError();
              }}
            />
          </React.Fragment>
        )}
      >
        <Text>{this.state.message}</Text>
        {/* on click, this button sets an Object */}
        {/* as a message, not a string. Which will cause */}
        {/* an error to occur in the component tree */}
        <Button
          title="Click here to change message!"
          onPress={() =>
            this.setState({ message: { text: "Hello World" } })
          }
        />
      </Sentry.ErrorBoundary>
    );
  }
}

export default MyComponent;
```

### [Using multiple error boundaries](https://docs.sentry.io/platforms/react-native/integrations/error-boundary.md#using-multiple-error-boundaries)

When using multiple error boundaries, we recommend using `beforeCapture` to set tags/context so that you can tell which error boundary the error occurred from. In the example below, we attach tags to errors based on what route they rendered in:

```javascript
import React from "react";
import { View, Text } from "react-native";
import * as Sentry from "@sentry/react-native";

function MyComponent({ props }) {
  return (
    <React.Fragment>
      <Sentry.ErrorBoundary
        beforeCapture={(scope) => {
          scope.setTag("location", "first");
          scope.setTag("anotherTag", "anotherValue");
        }}
      >
        <View>
          <Text>First</Text>
        </View>
      </Sentry.ErrorBoundary>
      <Sentry.ErrorBoundary
        beforeCapture={(scope) => {
          scope.setTag("location", "second");
        }}
      >
        <View>
          <Text>Second</Text>
        </View>
      </Sentry.ErrorBoundary>
    </React.Fragment>
  );
}

export default MyComponent;
```

## [Troubleshooting](https://docs.sentry.io/platforms/react-native/integrations/error-boundary.md#troubleshooting)

### [Fallback Not Rendering](https://docs.sentry.io/platforms/react-native/integrations/error-boundary.md#fallback-not-rendering)

If your `ErrorBoundary` fallback isn't appearing, make sure the error is happening **during rendering**. Errors thrown in event handlers (like `onPress`), `setTimeout`, `async` functions, or Promises won't trigger the fallback. See [Handling Non-Render Errors](https://docs.sentry.io/platforms/react-native/integrations/error-boundary.md#handling-non-render-errors).

To verify your ErrorBoundary is working, trigger a render error via component state:

```javascript
const [crash, setCrash] = useState(false);

if (crash) {
  throw new Error("Test render error");
}

return (
  <Button onPress={() => setCrash(true)} title="Test ErrorBoundary" />
);
```

### [Screenshots Capture the Fallback Instead of the Error](https://docs.sentry.io/platforms/react-native/integrations/error-boundary.md#screenshots-capture-the-fallback-instead-of-the-error)

When using `attachScreenshot: true` with `ErrorBoundary`, the captured screenshot may show the fallback component instead of the screen at the time of the error. This happens because the screenshot is taken shortly after the error is captured, by which time React has already rendered the fallback UI. This is a known limitation.