AI-powered crash analysis is now available on all plans — including Free.Read the crash analysis guide
Expo SDK

Crash Reporting for Expo Apps

Full crash coverage, session replay, and network monitoring for Expo managed and bare workflow apps. Compatible with EAS Build, Expo Router, and Expo Go. Privacy-first. No video recording.

3-step setup for Expo

1

Install

npx expo install @bugspulse/react-native

Works in both managed and bare workflow

2

Initialize in App.tsx

import BugsPulse from '@bugspulse/react-native';

BugsPulse.init({
  apiKey: 'bp_your_project_key',
  environment: process.env.APP_ENV ?? 'production',
  sessionReplay: true,
  captureNetworkRequests: true,
});

Call this before any other imports that might throw

3

Add Expo Router navigation tracking

// app/_layout.tsx (Expo Router)
import { useNavigationContainerRef } from 'expo-router';
import BugsPulse from '@bugspulse/react-native';

export default function RootLayout() {
  const ref = useNavigationContainerRef();

  useEffect(() => {
    if (ref) {
      BugsPulse.setNavigationRef(ref);
    }
  }, [ref]);

  return <Stack />;
}

Every route transition is recorded automatically

Built for how Expo apps work

Works with Expo managed workflow

No native module linking required for Expo managed projects. Install with npx expo install and configure in your entry file.

EAS Build compatible

Source maps generated by EAS Build are automatically uploadable to BugsPulse for symbolicated stack traces in production.

Expo Router support

Navigation tracking works with Expo Router — every route change is recorded automatically as a breadcrumb in the session timeline.

Event-based session replay

Replay sessions as structured event timelines: taps, navigation, network requests, and crash events. No video, no PII.

Network request monitoring

Every fetch call is recorded with URL, method, status, and duration. Find the failed API request that caused the blank screen or crash.

Privacy-safe for App Store

No IDFA, no video, no device tracking. Your Expo app's App Store privacy label stays minimal and compliant.

Source maps with EAS Build

EAS Build can generate source maps for your JavaScript bundle. Add this to your eas.json to ensure source maps are generated on every production build:

# eas.json

{
  "build": {
    "production": {
      "env": {
        "APP_ENV": "production"
      },
      "android": {
        "buildType": "apk"
      }
    }
  }
}

Upload source maps to BugsPulse via the CLI after each EAS Build to get symbolicated stack traces in production crash reports.

# Upload source maps (CI/CD step)

npx bugspulse-cli upload-sourcemaps \
  --version $APP_VERSION \
  --bundle ./dist/index.js \
  --sourcemap ./dist/index.js.map

Start monitoring your Expo app

Free plan includes 1,500 sessions/month. No credit card required.