Sentry-Expo Build Error: '@sentry/cli' File Not Found in Monorepo

[sajadghawami]

Issue Description

In our monorepo setup, we are encountering a build error with sentry-expo. The error occurs during the build step, specifically at the Upload Debug Symbols to Sentry stage. The error message displayed is ../node_modules/@sentry/cli/bin/sentry-cli: No such file or directory, followed by error: API request failed. This issue is preventing us from successfully completing our build process.

I am pretty sure it has to do with our monorepo setup and that the node_modules are not where they are expected to be.

Expected Behavior

The expected behavior is that the build should complete successfully, including the uploading of debug symbols to Sentry without any errors.

Actual Behavior

Instead of a successful build, the process fails at the 'Upload Debug Symbols to Sentry' step. The error reported is ../node_modules/@sentry/cli/bin/sentry-cli: No such file or directory, which is immediately followed by error: API request failed.

Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!

bare

What platform(s) does this occur on?

Android, iOS

SDK Version (managed workflow only)

~48.0.18

Environment

Environment Details

{
"expo": "48.0.18",
"react-native": "0.71.8",
"sentry-expo": "6.2.0",
"expo-application": "5.1.1",
"expo-constants": "14.2.1",
"expo-device": "5.2.1",
"@sentry/react-native": "4.15.2"
}

Reproducible demo or steps to reproduce from a blank project

1. In a monorepo setup, where the app is in /apps/app In the project directory, install sentry-expo using the command:

   npx expo install sentry-expo

2. Install the additional required Expo module packages with:

   
   npx expo install expo-application expo-constants expo-device @sentry/react-native

[github-actions[bot]]

This issue is stale because it has been open for 60 days with no activity. If there is no activity in the next 7 days, the issue will be closed.

[github-actions[bot]]

This issue was closed because it has been inactive for 7 days since being marked as stale. Please open a new issue if you believe you are encountering a related problem.