workspace is not supported (as per 7.8.0)

[bondarenkod]

What React Native libraries do you use?

React Native (no additional frameworks)

Are you using sentry.io or on-premise?

sentry.io (SaaS)

@sentry/react-native SDK Version

7.8.0

How does your development environment look like?

This likely isn’t relevant to the issue, but included for completeness.

System:
  OS: Windows 11 10.0.26200
  CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H
  Memory: 32.19 GB / 63.71 GB
Binaries:
  Node:
    version: 22.18.0
    path: C:\Users\DARPA\AppData\Roaming\fnm\node-versions\v22.18.0\installation\node.EXE
  Yarn:
    version: 4.12.0
    path: C:\Users\DARPA\AppData\Roaming\fnm\node-versions\v22.18.0\installation\yarn.CMD
  npm:
    version: 10.9.3
    path: C:\Users\DARPA\AppData\Roaming\fnm\node-versions\v22.18.0\installation\npm.CMD
  Watchman: Not Found
SDKs:
  Android SDK:
    API Levels:
      - "33"
      - "34"
      - "35"
      - "36"
    Build Tools:
      - 33.0.0
      - 34.0.0
      - 35.0.0
      - 35.0.1
      - 36.0.0
    System Images:
      - android-34 | Google Play Intel x86_64 Atom
      - android-35 | Google Play Intel x86_64 Atom
      - android-36 | Google Play Intel x86_64 Atom
    Android NDK: Not Found
  Windows SDK: Not Found
IDEs:
  Android Studio: Not Found
  Visual Studio:
    - 17.14.36705.20 (Visual Studio Community 2022)
Languages:
  Java:
    version: 17.0.17
    path: C:\Program Files\Microsoft\jdk-17.0.17.10-hotspot\bin\javac.EXE
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 19.2.0
    wanted: 19.2.0
  react-native:
    installed: 0.83.1
    wanted: ^0.83.0
  react-native-windows: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

Sentry.init()

Sentry.init({
  dsn: 'https://...@sentry.io/...',
  // other options
});

Steps to Reproduce

1. Create a workspace-based (monorepo) project using Yarn Berry.
2. Use a workspace structure similar to the following (note: node_modules is at the repository root):

/root
  /mobile
    /RNBasedMobileApplication  <- React Native app (supported by RN for a long time, at least since ~0.73)
  /infrastructure
  /common
  /web
  /node_modules               <- node_modules directory is here
  package.json

3. Install and configure an older @sentry/react-native version (e.g., 7.7.0). The iOS build works with this file structure.

4. Upgrade to @sentry/react-native 7.8.0 and build for iOS. The build fails (see “Actual Result”).

5. Ensure you enable debug logs by adding the following to .xcode.env:

   • export SENTRY_LOG_LEVEL=debug

Additional Context

It appears that a recent change hard-codes the default path to the React Native Xcode script as:

REACT_NATIVE_XCODE_DEFAULT="../node_modules/react-native/scripts/react-native-xcode.sh"

In a workspace/monorepo where node_modules is located at the repository root, this relative path can become invalid. Related change:
459a438#diff-adc0bbd34cc2ce0ddb7585ef1c52dd0cf4706cf97c701a0962b6679daa29fe1f

Expected Result

1. Sentry should support workspace/monorepo React Native projects where node_modules is located at the repository root (a common Yarn Berry / workspace setup).

2. Any breaking changes should be clearly documented in release notes.

   • In particular, changes affecting the Xcode build phase integration should be explicitly called out and accompanied by:

     • a clear warning / migration note, and ideally
     • an auto-migration, or at minimum a deliberate, actionable failure message during install/build indicating exactly what to change.

This kind of behavior was not expected for a minor version update.

Actual Result

iOS build error:

++ echo 'error: sentry-cli - REACT_NATIVE_XCODE script not found at: /Users/DARPA/Documents/src/rn01/mobile/EYE/node_modules/react-native/scripts/react-native-xcode.sh'

Additionally (likely related), in CI when SENTRY_LOG_LEVEL is not set, the logs are much less actionable and the build fails with a large set of errors, for example:

error export CLANG_WARN_DOCUMENTATION_COMMENTS\=YES
error export CLANG_WARN_QUOTED_INCLUDE_IN_FRAMEWORK_HEADER\=NO
error export GCC_WARN_INHIBIT_ALL_WARNINGS\=YES
error export VALIDATE_PRODUCT\=YES
error .h /Users/DARPA/azba/MacMini-VM12-01/_work/2/s/DARPACore.ReactNative/mobile/DemoApp2/ios/Pods/SDWebImage/SDWebImage/Core/SDWebImageError.h (in target 'SDWebImage' from project 'Pods')
error .h /Users/DARPA/azba/MacMini-VM12-01/_work/2/s/DARPACore.ReactNative/mobile/DemoApp2/ios/obj/Build/Intermediates.noindex/ArchiveIntermediates/DemoApp2/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/SDWebImage.framework/Headers
error .h /Users/DARPA/azba/MacMini-VM12-01/_work/2/s/DARPACore.ReactNative/node_modules/react-native/ReactCommon/cxxreact/RecoverableError.h (in target 'React-cxxreact' from project 'Pods')
error .h /Users/DARPA/azba/MacMini-VM12-01/_work/2/s/DARPACore.ReactNative/mobile/DemoApp2/ios/obj/Build/Intermediates.noindex/ArchiveIntermediates/DemoApp2/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/cxxreact.framework/Headers
error .h /Users/DARPA/azba/MacMini-VM12-01/_work/2/s/DARPACore.ReactNative/mobile/DemoApp2/ios/Pods/PromisesObjC/Sources/FBLPromises/include/FBLPromiseError.h (in target 'PromisesObjC' from project 'Pods')
error .h /Users/DARPA/azba/MacMini-VM12-01/_work/2/s/DARPACore.ReactNative/mobile/DemoApp2/ios/obj/Build/Intermediates.noindex/ArchiveIntermediates/DemoApp2/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/FBLPromises.framework/Headers
error .h /Users/DARPA/azba/MacMini-VM12-01/_work/2/s/DARPACore.ReactNative/mobile/DemoApp2/ios/Pods/AppAuth/Sources/AppAuthCore/OIDError.h (in target 'AppAuth' from project 'Pods')
error .h /Users/DARPA/azba/MacMini-VM12-01/_work/2/s/DARPACore.ReactNative/mobile/DemoApp2/ios/obj/Build/Intermediates.noindex/ArchiveIntermediates/DemoApp2/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/AppAuth.framework/Headers

[linear]

RN-450

[bondarenkod]

Suggested changes:

• introduce the ability to resolve the node_modules path in a dynamic way, avoid creating static references on the files\directories in a future.
• Add a validation step to check if the resolved path actually exists
• Introduce an ability to override node_modules initial path using the env variables: export SENTRY_NODE_MODULES_PATH_OVERRIDE="../../../node_modules"
  Here is my draft version of the file:

#!/bin/bash
# Sentry Bundle React Native code and images
# PWD=ios

# print commands before executing them and stop on first error
set -x -e

# WITH_ENVIRONMENT is executed by React Native

LOCAL_NODE_BINARY=${NODE_BINARY:-node}

# The project root by default is one level up from the ios directory
RN_PROJECT_ROOT="${PROJECT_DIR}/.."

[ -z "$SENTRY_PROPERTIES" ] && export SENTRY_PROPERTIES=sentry.properties
[ -z "$SENTRY_DOTENV_PATH" ] && [ -f "$RN_PROJECT_ROOT/.env.sentry-build-plugin" ] && export SENTRY_DOTENV_PATH="$RN_PROJECT_ROOT/.env.sentry-build-plugin"
[ -z "$SOURCEMAP_FILE" ] && export SOURCEMAP_FILE="$DERIVED_FILE_DIR/main.jsbundle.map"

if [ -z "$SENTRY_CLI_EXECUTABLE" ]; then
  # Try standard resolution safely
  RESOLVED_PATH=$(
    "$LOCAL_NODE_BINARY" --print "require('path').dirname(require.resolve('@sentry/cli/package.json'))" 2>/dev/null
  ) || true
  if [ -n "$RESOLVED_PATH" ]; then
    SENTRY_CLI_PACKAGE_PATH="$RESOLVED_PATH/bin/sentry-cli"
  else
    # Fallback: parse NODE_PATH from the .bin/sentry-cli shim (file generated by PNPM)
    PNPM_BIN_PATH="$PWD/../node_modules/@sentry/react-native/node_modules/.bin/sentry-cli"

    if [ -f "$PNPM_BIN_PATH" ]; then
      CLI_FILE_TEXT=$(cat "$PNPM_BIN_PATH")

      # Filter where PNPM stored Sentry CLI
      NODE_PATH_LINE=$(echo "$CLI_FILE_TEXT" | grep -oE 'NODE_PATH="[^"]+"' | head -n1)
      NODE_PATH_VALUE=$(echo "$NODE_PATH_LINE" | sed -E 's/^NODE_PATH="([^"]+)".*/\1/')
      SENTRY_CLI_PACKAGE_PATH=${NODE_PATH_VALUE%%/bin*}
    fi
  fi
fi
[ -z "$SENTRY_CLI_EXECUTABLE" ] && SENTRY_CLI_EXECUTABLE="$SENTRY_CLI_PACKAGE_PATH"

NODE_MODULES_PATH_DEFAULT="../node_modules"

# Override order for node_modules:
# 1) env var SENTRY_NODE_MODULES_PATH_OVERRIDE (if set)
# 2) default path
NODE_MODULES_PATH_INPUT="${SENTRY_NODE_MODULES_PATH_OVERRIDE:-$NODE_MODULES_PATH_DEFAULT}"

# Resolve node_modules path to an absolute path (relative paths are interpreted from the current working directory, typically the ios/ folder).
NODE_MODULES_PATH=$(
  "$LOCAL_NODE_BINARY" -e "const path=require('path'); console.log(path.resolve(process.cwd(), process.argv[1]));" "$NODE_MODULES_PATH_INPUT"
)

echo "output: sentry-cli - NODE_MODULES_PATH resolved to $NODE_MODULES_PATH"

if [ ! -d "$NODE_MODULES_PATH" ]; then
  echo "error: sentry-cli - node_modules folder not found at: $NODE_MODULES_PATH"
  echo "error: sentry-cli - Original input: $NODE_MODULES_PATH_INPUT"
  exit 1
fi

REACT_NATIVE_XCODE_DEFAULT="$NODE_MODULES_PATH/react-native/scripts/react-native-xcode.sh"

# Override order for the react-native-xcode.sh script:
# 1) first script arg ($1)
# 2) dynamically built default (from NODE_MODULES_PATH)
REACT_NATIVE_XCODE_INPUT="${1:-$REACT_NATIVE_XCODE_DEFAULT}"

# Resolve to an absolute path (handles if $1 is relative).
REACT_NATIVE_XCODE=$(
  "$LOCAL_NODE_BINARY" -e "const path=require('path'); console.log(path.resolve(process.cwd(), process.argv[1]));" "$REACT_NATIVE_XCODE_INPUT"
)

echo "output: sentry-cli - REACT_NATIVE_XCODE resolved to $REACT_NATIVE_XCODE"

if [ ! -f "$REACT_NATIVE_XCODE" ]; then
  echo "error: sentry-cli - REACT_NATIVE_XCODE script not found at: $REACT_NATIVE_XCODE"
  echo "error: sentry-cli - Original input: $REACT_NATIVE_XCODE_INPUT"
  exit 1
fi

[[ "$AUTO_RELEASE" == false ]] && [[ -z "$BUNDLE_COMMAND" || "$BUNDLE_COMMAND" != "ram-bundle" ]] && NO_AUTO_RELEASE="--no-auto-release"
ARGS="$NO_AUTO_RELEASE $SENTRY_CLI_EXTRA_ARGS $SENTRY_CLI_RN_XCODE_EXTRA_ARGS"

REACT_NATIVE_XCODE_WITH_SENTRY="\"$SENTRY_CLI_EXECUTABLE\" react-native xcode $ARGS \"$REACT_NATIVE_XCODE\""

exitCode=0

if [ "$SENTRY_DISABLE_AUTO_UPLOAD" != true ]; then
  # 'warning:' triggers a warning in Xcode, 'error:' triggers an error
  set +x +e # disable printing commands otherwise we might print `error:` by accident and allow continuing on error
  SENTRY_XCODE_COMMAND_OUTPUT=$(/bin/sh -c "\"$LOCAL_NODE_BINARY\" $REACT_NATIVE_XCODE_WITH_SENTRY" 2>&1)
  if [ $? -eq 0 ]; then
    echo "$SENTRY_XCODE_COMMAND_OUTPUT" | awk '{print "output: sentry-cli - " $0}'
  else
    echo "error: sentry-cli - To disable source maps auto upload, set SENTRY_DISABLE_AUTO_UPLOAD=true in your environment variables. Or to allow failing upload, set SENTRY_ALLOW_FAILURE=true"
    echo "error: sentry-cli - $SENTRY_XCODE_COMMAND_OUTPUT"
    exitCode=1
  fi
  set -x -e # re-enable
else
  echo "SENTRY_DISABLE_AUTO_UPLOAD=true, skipping sourcemaps upload"
  /bin/sh -c "$REACT_NATIVE_XCODE"
fi

[ -z "$SENTRY_COLLECT_MODULES" ] && SENTRY_RN_PACKAGE_PATH=$("$LOCAL_NODE_BINARY" --print "require('path').dirname(require.resolve('@sentry/react-native/package.json'))")
[ -z "$SENTRY_COLLECT_MODULES" ] && SENTRY_COLLECT_MODULES="${SENTRY_RN_PACKAGE_PATH}/scripts/collect-modules.sh"

if [ -f "$SENTRY_COLLECT_MODULES" ]; then
  /bin/sh "$SENTRY_COLLECT_MODULES"
fi

exit $exitCode

• It is possible to create a pr, but I need time to review, improve this file further, because a few conditional code branches will fail. Ping me if you agree/want to get a PR from me.

• it is possible that this issue is related to a few other recently opened issues here.

[bondarenkod]

Regarding the breaking changes (in my opinion) of the xcode build stage integration:
459a438#diff-3ffd9c71352b62c3e3183a7b61560472ee0725212d3d90e687d1e7936022cccb
It is possible that the next error was due to the old style (which was valid for the previous version of the package)

error export CLANG_WARN_DOCUMENTATION_COMMENTS\=YES
error export CLANG_WARN_QUOTED_INCLUDE_IN_FRAMEWORK_HEADER\=NO
error export GCC_WARN_INHIBIT_ALL_WARNINGS\=YES
error export VALIDATE_PRODUCT\=YES
.... see above the rest of the log

[bondarenkod]

With the provided patch and applying xcode build stage integration changes I finally being able to run the app without native crash.

[antonis]

Thank you for reporting and your suggestions @bondarenkod 🙇 We will investigate this and iterate back.

[bondarenkod]

Thank you for reporting and your suggestions @bondarenkod 🙇 We will investigate this and iterate back.

Glad to help!
Ping\Contact me if you need something\have any questions.