This documentation is available as Markdown for AI agents and LLMs. See the full Markdown index or append .md to any documentation URL.

Report Reanimated errors and warnings from your production app by enabling the Reanimated integration for EAS Observe.

expo-observe ships an opt-in integration for react-native-reanimated that reports Reanimated errors and warnings to EAS Observe. Reanimated prints these messages only to the console, so without the integration you cannot see them for devices in production. The integration reports each Reanimated error as a reanimated.error error. It can also log each Reanimated warning as a reanimated.warning event.

Prerequisites

Enable the integration

Call Observe.configure() once with the react-native-reanimated integration flag at module scope, before your app mounts:

import { Observe } from 'expo-observe';

Observe.configure({
  integrations: { 'react-native-reanimated': true },
});

No other setup is needed. Once enabled, the integration reports Reanimated errors automatically.

The integration configures Reanimated's logger itself with configureReanimatedLogger. Do not call configureReanimatedLogger in your app:

• A call after Observe.configure() removes the integration's callback, and the integration stops reporting.
• A call before Observe.configure() loses its level and strict options, because the integration replaces them.

To set the logger's level and strict options, or to enable warnings, follow the instructions in the configuration section below.

Configuration

Pass a configuration object instead of true to set the logger options or to report warnings:

import { Observe } from 'expo-observe';
import { ReanimatedLogLevel } from 'react-native-reanimated';

Observe.configure({
  integrations: {
    'react-native-reanimated': {
      level: ReanimatedLogLevel.warn,
      strict: true,
      reportWarnings: true,
    },
  },
});

• level: The minimum log level that Reanimated prints and reports. Use ReanimatedLogLevel.warn or ReanimatedLogLevel.error. The default is ReanimatedLogLevel.warn.
• strict: Whether Reanimated also prints and reports its strict-mode warnings. The default is true.
• reportWarnings: Whether the integration also reports Reanimated warnings to EAS Observe as reanimated.warning events. The default is false. Reanimated prints warnings to the console either way.

To turn off reporting, call Observe.configure() again without the react-native-reanimated integration. Reanimated's logger keeps its level and strict options.

How it works

Reanimated calls the integration for each message that passes its logger's level and strict settings. This includes messages from the React Native runtime and from the UI runtime. Reanimated still prints all errors and warnings to the console.

The integration reports a Reanimated error as a non-fatal error named reanimated.error. It appears with your other errors in the Errors page. See Error reporting.

• For an error on the React Native runtime, the stack trace starts in Reanimated's logger and then includes the code that called the logger.
• For an error on the UI runtime, Reanimated delivers the message later, so the error has the message but no stack trace.

When reportWarnings is true, the integration logs a Reanimated warning as a reanimated.warning event with warn severity.

Event attributes:

Some Reanimated messages, such as warnings from measure(), can repeat on every frame. To limit the number of reports, the integration applies these limits in a 15-minute period:

• Each distinct message is reported at most once.
• At most 20 distinct errors and 20 distinct warnings are reported. Errors and warnings have separate limits, so many warnings cannot stop errors from being reported.

Messages are compared by their first 500 characters.

View errors and events

In the dashboard: open your project and navigate to Observe > Errors to see reanimated.error errors. Navigate to Observe > Events and select the reanimated.warning event to see individual warnings with their attributes and sessions.

From the CLI:

For naming, severity, and attribute details shared by all events, see User-defined events.