fix(expo): resolve plugin config when registered as bare '@sentry/react-native'

CHANGELOG.md

@@ -31,6 +31,11 @@
 
   Apps on the Old Architecture now get the same aggregate, span attribution and slow call breadcrumbs as TurboModules. An `arch: 'new' | 'legacy'` field distinguishes the two sources. Opt in with `turboModuleContextIntegration({ enableLegacyNativeModules: true })`.
 
+
+### Fixes
+
+- `sentry-expo-upload-sourcemaps` now reads plugin config when the plugin is registered as `@sentry/react-native` ([#6543](https://github.com/getsentry/sentry-react-native/pull/6543))
+
 ### Dependencies
 
 - Bump Android SDK from v8.50.1 to v8.51.0 ([#6539](https://github.com/getsentry/sentry-react-native/pull/6539))

packages/expo-upload-sourcemaps/cli.js

@@ -60,7 +60,9 @@ function getSentryPluginPropertiesFromExpoConfig() {
         return false;
       }
       const [pluginName] = plugin;
-      return pluginName === '@sentry/react-native/expo';
+      // Both '@sentry/react-native' and '@sentry/react-native/expo' are valid
+      // plugin paths in the Expo config; Expo resolves them the same way.
+      return pluginName === '@sentry/react-native/expo' || pluginName === '@sentry/react-native';
     });
 
     if (sentryPlugin) {