-
-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XCode Build Fails: PhaseScriptExecution failed with a nonzero exit code #948
Comments
@karlludwigweise do You have any solutions? I have this errors to. System: REACT_NATIVE: |
@karlludwigweise remove derivedData, clean build. build phases
Bundle React Native code and images =>
I hope it helps You to. |
@sprotymo what's the build phases part? Is that your |
@karlludwigweise |
Well, that works like a charm. Where did you get that info? I guess it is a problem when using Node with a version manager. Thanks 🙏 |
Hi guys, looks like everything is solved, are we good to close this? |
found by chance, in the link to the official documentation and possible problems with nvm |
I would throw in a missing documentation on https://docs.sentry.io/platforms/react-native/ but otherwise I'm good with closing it. 👍 |
EDIT: If anyone is looking for the original info: #141 |
I am working on an ejected Expo App in the bare workflow and applied the first part of @sprotymo solution and it works! Thanks! In
I don't have a |
@sprotymo - this guys solution worked for me. though i didnt have to clean adn reinstall everything
Note append the above to the beginning of those sections - before the existing script that must already be present in those sections. I am guessing the issue is with using nvm. scripts added by sentry wizard are not able to locate node binaries when you use nvm |
I was using nvm and non of solutions worked for me So looking in docs I found this solution: https://docs.sentry.io/clients/react-native/manual-setup/#using-node-with-nvm-or-notion Basically I set the scripts like this Bundle React Native code and images
Upload Debug Symbols to Sentry
|
@andru1989 thank you. I prefer this one over the solutions above, because it does not mess with device build via xcode. |
This is made my xcode see the node. |
xcode 12 Took a few hours to debug, finally got it working with the following scripts: Bundle React Native code and images
Upload Debug Symbols to Sentry
Hope these help guys! |
Very good and clean solution. Worked |
Bundle React Native code and images
|
Hi folks! Just replace this |
Facing this same issue in my CLI.
|
This solution worked for me : |
It worked for me. I am using Mac Mini with M1 chipset |
Best solution, it worked for me, thank you very much |
Worked for me
Nice one man! Worked for me! |
This workaround is already documented here https://docs.sentry.io/platforms/react-native/troubleshooting/#using-node-with-nvm-or-volta |
OS:
Platform:
SDK:
@sentry/react-native
(>= 1.0.0)react-native-sentry
(<= 0.43.2)SDK version: 15.0.0
react-native
version: 0.62.2Are you using Expo?
Are you using sentry.io or on-premise?
Configuration:
(
@sentry/react-native
)I have following issue:
Building an iOS App Sentry fails with:
env: node: No such file or directory Command PhaseScriptExecution failed with a nonzero exit code
Executing
/bin/sh -c /Users/{USERNAME}/Library/Developer/Xcode/DerivedData/{ID}/Build/Intermediates.noindex/{APP}.build/Release-iphoneos/{APP}.build/Script-00DD1BFF1BD5951E006B06BC.sh
in on the console will throw the following error:line 5: ../node_modules/@sentry/cli/bin/sentry-cli: No such file or directory
Steps to reproduce:
Following the setup on https://docs.sentry.io/platforms/react-native/
yarn add @sentry/react-native
yarn sentry-wizard -i reactNative -p ios android
cd ios && pod install
Connecting the SDK to Sentry and verifying it in DEV Mode works fine.
In XCode:
localhost
fromApp Transport Security Settings
Actual result:
Build fails
env: node: No such file or directory Command PhaseScriptExecution failed with a nonzero exit code
Expected result:
Build runs successfully.
The text was updated successfully, but these errors were encountered: