What React Native libraries do you use?
React Navigation, Hermes, Expo (mobile only), Expo Web, React Native Web
Are you using sentry.io or on-premise?
sentry.io (SaS)
Are you using any other error monitoring solution alongside Sentry?
No
Other Error Monitoring Solution Name
No response
@sentry/react-native SDK Version
6.20.0
How does your development environment look like?
expo-env-info 2.0.12 environment info:
System:
OS: macOS 26.4.1
Shell: 5.9 - /bin/zsh
Binaries:
Node: 24.15.0 - ~/Documents/Programming/bluesky-social/social-app/node_modules/.bin/node
npm: 11.12.1 - ~/.nvm/versions/node/v24.15.0/bin/npm
Watchman: 2026.05.11.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.16.2 - /Users/samuel/.rbenv/shims/pod
SDKs:
iOS SDK:
Platforms: DriverKit 25.5, iOS 26.5, macOS 26.5, tvOS 26.5, visionOS 26.5, watchOS 26.5
Android SDK:
API Levels: 29, 33, 34, 35, 36
Build Tools: 30.0.3, 34.0.0, 35.0.0, 35.0.1, 36.0.0
System Images: android-28 | Google ARM64-V8a Play ARM 64 v8a, android-29 | Google Play ARM 64 v8a, android-30 | Google APIs ARM 64 v8a, android-34 | Google Play ARM 64 v8a, android-35 | Google Play ARM 64 v8a, android-36 | Google Play ARM 64 v8a
IDEs:
Android Studio: 2025.3 AI-253.32098.37.2534.15232325
Xcode: 26.5/17F42 - /usr/bin/xcodebuild
npmPackages:
@expo/webpack-config: ^19.0.1 => 19.0.1
babel-preset-expo: ~54.0.10 => 54.0.10
expo: 54.0.34 => 54.0.34
expo-updates: ~29.0.17 => 29.0.17
react: 19.1.0 => 19.1.0
react-dom: 19.1.0 => 19.1.0
react-native: 0.81.5 => 0.81.5
react-native-web: ^0.21.0 => 0.21.2
Expo Workflow: bare
Sentry.init()
init({
enabled: !env.IS_DEV && !!env.SENTRY_DSN,
autoSessionTracking: false,
dsn: env.SENTRY_DSN,
debug: false, // If `true`, Sentry will try to print out useful debugging information if something goes wrong with sending the event. Set it to `false` in production
environment: env.ENV,
dist: env.BUNDLE_IDENTIFIER,
release: env.RELEASE_VERSION,
ignoreErrors: [
/*
* Unknown internals errors
*/
`t is not defined`,
`Can't find variable: t`,
/*
* Un-useful errors
*/
`Network request failed`,
],
/**
* Does not affect traces of error events or other logs, just disables
* automatically attaching stack traces to events. This helps us group events
* and prevents explosions of separate issues.
*
* @see https://docs.sentry.io/platforms/react-native/configuration/options/#attach-stacktrace
*/
attachStacktrace: false,
sampleRate: env.IS_INTERNAL ? 1.0 : 0.1,
})
Steps to Reproduce
- Enforce use of pnpm in package.json via
devEngines.packageManager
"devEngines": {
"packageManager": {
"name": "pnpm",
"onFail": "error"
}
},
- Try and run sourcemap script. It fails due to hardcoded use of
npx here:
|
const result = spawnSync('npx', ['expo', 'config', '--json'], { encoding: 'utf8' }); |
Expected Result
it works
Actual Result
$ sentry-expo-upload-sourcemaps dist
env: load .env
env: export EXPO_PUBLIC_ENV EXPO_PUBLIC_BUNDLE_DATE EXPO_PUBLIC_LOG_LEVEL EXPO_PUBLIC_LOG_DEBUG CROWDIN_PERSONAL_TOKEN
🐕 Fetching from expo config...
npm error code EBADDEVENGINES
npm error EBADDEVENGINES The developer of this package has specified the following through devEngines
npm error EBADDEVENGINES Invalid devEngines.packageManager
npm error EBADDEVENGINES Invalid name "pnpm" does not match "npm" for "packageManager"
npm error EBADDEVENGINES {
npm error EBADDEVENGINES current: { name: 'npm', version: '11.12.1' },
npm error EBADDEVENGINES required: { name: 'pnpm', onFail: 'error' }
npm error EBADDEVENGINES }
npm error A complete log of this run can be found in: /Users/samuel/.npm/_logs/2026-05-15T16_12_54_081Z-debug-0.log
What React Native libraries do you use?
React Navigation, Hermes, Expo (mobile only), Expo Web, React Native Web
Are you using sentry.io or on-premise?
sentry.io (SaS)
Are you using any other error monitoring solution alongside Sentry?
No
Other Error Monitoring Solution Name
No response
@sentry/react-native SDK Version
6.20.0
How does your development environment look like?
Sentry.init()
Steps to Reproduce
devEngines.packageManagernpxhere:sentry-react-native/packages/expo-upload-sourcemaps/cli.js
Line 19 in 9210ae6
Expected Result
it works
Actual Result