Command PhaseScriptExecution failed with a nonzero exit code

[lucas-zijian-zhu]

Description

I followed the instructions from https://reactnative.dev/docs/environment-setup

npx react-native init AwesomeProject
npm install then cd to ios directory and run
pod install
then opened the project with Xcode and trigged build. But the build failed and the error is
Command PhaseScriptExecution failed with a nonzero exit code
The project could run properly via the command npx react-native run-ios, but could not be built on Xcode, I tried on two different Macbook and got the same error.

Version

0.67.1

Output of npx react-native info

System:
OS: macOS 11.6.2
CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
Memory: 126.16 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 14.18.3 - ~/.nvm/versions/node/v14.18.3/bin/node
Yarn: 1.22.15 - /opt/local/bin/yarn
npm: 6.14.15 - ~/.nvm/versions/node/v14.18.3/bin/npm
Watchman: 2022.01.24.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.0.1, iOS 15.0, macOS 12.0, tvOS 15.0, watchOS 8.0
Android SDK: Not Found
IDEs:
Android Studio: 2020.3 AI-203.7717.56.2031.7784292
Xcode: 13.1/13A1030d - /usr/bin/xcodebuild
Languages:
Java: 11.0.13 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.67.1 => 0.67.1
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found

Steps to reproduce

npx react-native init AwesomeProject
npm install then cd to ios directory and run
pod install
then opened the project with Xcode and trigged build

Snack, code example, screenshot, or link to a repository

[dehlen]

Seeing the sample problem. Seems like this run script phase fails due to the latest changes made in RCTActionSheetIOS:

/Users/<redacted>/Developer/app.git-worktrees/feature/branch_name/node_modules/react-native/React/CoreModules/RCTActionSheetManager.mm:98:35: No member named 'cancelButtonTintColor' in 'JS::NativeActionSheetManager::SpecShowActionSheetWithOptionsOptions'

When I look at the FBReactNativeSpec header indeed the new property cancelButtonTintColor is missing.

[JonnyLinja]

I had what appears to be the same issue. Looks to be the same issue as #32951 which shows other people have it too. I am also attempting to run the project via Xcode directly.

#32712 solved it for me, which is slated for the 0.68 release. For now I temporarily patch-package'd the relevant changes to node_modules/react-native/scripts/find-node.sh to get 0.67.1 running.

[lucas-zijian-zhu]

@dehlen @JonnyLinja
This solution works for me:
https://stackoverflow.com/questions/66742033/phasescriptexecution-cp-user-error-in-react-native/70104375#70104375

[dehlen]

I do not use nvm but asdf-vm to manage my node versions. What worked for me was to have a look at the node_modules/react-native/scripts/find-node.sh script and to make sure that the script can find my current node version. None of the both paths for asdf were available on my machine which is why I had this error. Once I symlinked my asdf.sh from . /usr/local/opt/asdf/libexec/asdf.sh to $HOME/.asdf/asdf.sh the build started to work for me.

[krlol]

Cleaning the project and re-running worked for me

[vaughnkoch]

@dehlen, @krlol, @JonnyLinja agreed that cleaning & rebuilding works at least to solve the cancelButtonTintColor issue - it looks like FBReactNativeSpec.h is generated on the fly. Cleaning the build regenerated that file for me.

[prenansantana]

For me worked with:
Added line 4 and edited line 16

Commented line 89

[aramyesildeniz]

After trying out all suggestions and different versions of tools such as XCode, nvm, yarn, node, etc., the only thing that worked for me was to downgrade react native.

In package.json:

"react-native": "0.66.4"

[surajSanwal]

This worked for me

https://stackoverflow.com/a/71392772/4030220

This is nothing just an issue with the scheme name for me, in my case my scheme name contains whitespace e.g. "ABC staging", which is not allowed, it got fixed after deleting and creating a new scheme with the name "ABC-staging".

in the case of react-native 0.67^, you may need to apply these changes as well

change line no 7 
set -e. ==> set +e 

in

node_modules/react-native/scripts/find-node.sh

then use patch-package using the following command :

npx patch-package react-native

this will create a patch file inside the patch folder in root, then you can add in the post-install script in package.json:

 "postinstall": "npx patch-package"

This command will run each time a new package is getting added to the project and auto-fix react-native find-node. sh.

[Amr1440]

Same issue for 1 week now i couldn't resolve it

[surajSanwal]

https://stackoverflow.com/a/71392772/4030220

@Amr1440 have you checked my comments, after 2 to 3 days of work I got the solution, the issue may be due to scheme name including special char or need a change in the react-native load script.

[pedrolopes10]

after some hours, uninstall node from brew and installed directly from node website and worked!

[Jafferson1]

This worked for me:
I changed MyProject/index.tsx to MyProject/index.js