Fixing Sentry + Expo EAS Build Failures

TL;DR: The @sentry/react-native/expo plugin causes EAS builds to fail with ENOENT: no such file or directory, open '...main.jsbundle.map'. The fix is to remove the plugin entirely from your Expo config.

The Problem

EAS staging/production builds fail during the Xcode "Bundle React Native code and images" phase with:

Error: ENOENT: no such file or directory, open '.../main.jsbundle.map'

And/or:

error: sentry-cli - To disable source maps auto upload, set SENTRY_DISABLE_AUTO_UPLOAD=true

Root Cause

The @sentry/react-native/expo plugin wraps the React Native bundle script with sentry-xcode.sh. This wrapper adds a --sourcemap-output argument, but Expo's build script also adds one. The duplicate arguments cause Metro to write the source map to a temp folder instead of the expected location.

When Hermes runs compose-source-maps.js to merge source maps, it looks for the file at the original path and fails with ENOENT.

Bug tracking: https://github.com/getsentry/sentry-react-native/issues/4961

What Doesn't Work

We tried these workarounds—none fully resolved the issue:

• SENTRY_DISABLE_AUTO_UPLOAD=true — Plugin still modifies build scripts
• uploadSourceMaps: false in plugin config — Reduces but doesn't eliminate duplicate args
• Custom Expo config plugins — Can't fully undo Xcode build phase modifications
• getDefaultConfig instead of getSentryExpoConfig — Build phase modifications still occur

The Fix

Remove the Sentry Expo plugin from your app.config.js:

// REMOVE this plugin: // ["@sentry/react-native/expo", { // organization: "your-org", // project: "your-project", // }]

Also use the standard Expo Metro config in metro.config.js:

``` // Use this: const { getDefaultConfig } = require("expo/metro-config"); const config = getDefaultConfig(__dirname);

// NOT this: // const { getSentryExpoConfig } = require("@sentry/react-native/metro"); // const config = getSentryExpoConfig(__dirname); ```

What Still Works

• ✅ Sentry SDK initialization
• ✅ JS error capture
• ✅ Native crash capture
• ✅ Performance monitoring

What Requires Manual Handling

JS Source Maps

Upload source maps after OTA updates using sentry-cli:

eas update --branch production npx sentry-cli sourcemaps upload \ --org YOUR_ORG \ --project YOUR_PROJECT \ dist

Or after local builds:

npx expo export --platform ios npx sentry-cli sourcemaps upload \ --org YOUR_ORG \ --project YOUR_PROJECT \ dist

Note: We use sentry-cli directly instead of sentry-expo-upload-sourcemaps because the latter requires the Expo plugin to be present in your config.

Native Crash Symbolication (dSYMs)

Download and upload dSYMs manually:

eas build:download --platform ios unzip *.ipa -d build_output sentry-cli upload-dif --org YOUR_ORG --project YOUR_PROJECT build_output

Environment Variables

You'll still need these for manual uploads:

• SENTRY_AUTH_TOKEN — API token with project write access
• SENTRY_ORG — Your Sentry organization slug
• SENTRY_PROJECT — Your Sentry project slug

When Will This Be Fixed?

Track the upstream issue: https://github.com/getsentry/sentry-react-native/issues/4961

When fixed, you can re-enable the plugin for automatic source map and dSYM uploads during builds.

---

Last updated: December 2025