Xcode 12.4 React native build failed in IOS Showing All Messages Command PhaseScriptExecution failed with a nonzero exit code

Question

i am new in react native i want to run react native app in IOS after react-native init, app not run in IOS show some error Showing All Messages bash: Native/social_login/socialLogin/node_modules/react-native/scripts/../Libraries: No such file or directory Command PhaseScriptExecution failed with a nonzero exit code and build failed please help me versions
"react": "17.0.1", "react-native": "0.64.0" command line tools : Xcode 12.4 (12D4e)

score 4 · Answer 1 · answered Mar 28 '21 at 13:26

This happened also to me upgrading from 0.63 to 0.64. After trying all solutions I followed a solution moving the folder to a directory where the path contain no spaces and it works and build the app successfully.

Solution to React Native 0.64 build fail

In order for this to work properly follow these steps:

If you previously installed a global react-native-cli package, please remove it as it may cause unexpected issues (i.e. npm uninstall -g react-native-cli)
Move the project folder in a path with no spaces (i.e. ~/sub folder name/ReactNativeApp won't work till you have spaces in the path, so move in a path like ~/folder/ReactNativeApp)
Then cd into the project folder and upgrade react native to the latest version with npx react-native upgrade and resolve conflicts if any
After upgrading remove the node_modules folder and the yarn.lock from the root and the podfile.lock and Pods folder from ios subfolder
Then cd back to the root and run yarn install && npx pod-install
Now run again your app in Xcode or your IDE and it works

Crazy and absurd that a space in the path-name could cause this issue

this was the case for me. I skipped the first step, but it still solved the issue. Grazie mile Giuseppe! — LeftyT, Apr 13 '21 at 23:02
This was the case for me as well, after renaming the project folder without spaces, and moving it into a path without spaces in pathname, did the trick — Appy Mango, May 04 '22 at 13:51
"Move the project folder in a path with no spaces" - This answer saves my day man, thank you Using: M1 Pro 2021, 16GB Ram & ReactNative version: 0.71.3 — Duy Dau Dzu, Feb 28 '23 at 18:24

Suraj Sanwal · Answer 2 · 2022-03-11T09:35:38.013

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.

Ridwan Ajibola · Answer 3 · 2021-03-25T19:57:37.577

2

Try to run pod install in ios folder

cd ios && pod install

Then when it's done go back to your main folder and run

yarn run ios

If that doesn't work, check out the solutions here

Xcode 10.2.1 Command PhaseScriptExecution failed with a nonzero exit code

edited Mar 25 '21 at 19:57

answered Mar 25 '21 at 19:49

Ridwan Ajibola

873
11
16

Stathis Ntonas · Answer 4 · 2021-04-06T14:50:40.577

There seems to be an issue with coreutils on macOS.

What fixed it for me is:

brew install coreutils
brew install findutils
brew install gnu-sed

Finally change the node_modules/react-native/scripts/generate-specs.sh to:


#!/bin/bash
# Copyright (c) Facebook, Inc. and its affiliates.
#
# This source code is licensed under the MIT license found in the
# LICENSE file in the root directory of this source tree.

# This script collects the JavaScript spec definitions for core
# native modules and components, then uses react-native-codegen
# to generate native code.
#
# Optionally, set these envvars to override defaults:
# - SRCS_DIR: Path to JavaScript sources
# - CODEGEN_MODULES_LIBRARY_NAME: Defaults to FBReactNativeSpec
# - CODEGEN_MODULES_OUTPUT_DIR: Defaults to React/$CODEGEN_MODULES_LIBRARY_NAME/$CODEGEN_MODULES_LIBRARY_NAME
# - CODEGEN_COMPONENTS_LIBRARY_NAME: Defaults to rncore
# - CODEGEN_COMPONENTS_OUTPUT_DIR: Defaults to ReactCommon/react/renderer/components/$CODEGEN_COMPONENTS_LIBRARY_NAME
#
# Usage:
#   ./scripts/generate-specs.sh
#   SRCS_DIR=myapp/js CODEGEN_MODULES_LIBRARY_NAME=MySpecs CODEGEN_MODULES_OUTPUT_DIR=myapp/MySpecs ./scripts/generate-specs.sh
#

# shellcheck disable=SC2038

set -e

THIS_DIR=$(cd -P "$(gdirname "$(greadlink "${BASH_SOURCE[0]}" || echo "${BASH_SOURCE[0]}")")" && pwd)
TEMP_DIR=$(gmktemp -d /tmp/react-native-codegen-XXXXXXXX)
RN_DIR=$(cd "$THIS_DIR/.." && pwd)

# find node path
source "$RN_DIR/scripts/find-node.sh"

NODE_BINARY="${NODE_BINARY:-$(command -v node || true)}"
USE_FABRIC="${USE_FABRIC:-0}"

cleanup () {
  set +e
  grm -rf "$TEMP_DIR"
  set -e
}

describe () {
  printf "\\n\\n>>>>> %s\\n\\n\\n" "$1"
}

main() {
  SRCS_DIR=${SRCS_DIR:-$(cd "$RN_DIR/Libraries" && pwd)}
  CODEGEN_MODULES_LIBRARY_NAME=${CODEGEN_MODULES_LIBRARY_NAME:-FBReactNativeSpec}

  CODEGEN_COMPONENTS_LIBRARY_NAME=${CODEGEN_COMPONENTS_LIBRARY_NAME:-rncore}
  CODEGEN_MODULES_OUTPUT_DIR=${CODEGEN_MODULES_OUTPUT_DIR:-"$RN_DIR/React/$CODEGEN_MODULES_LIBRARY_NAME/$CODEGEN_MODULES_LIBRARY_NAME"}
  # TODO: $CODEGEN_COMPONENTS_PATH should be programmatically specified, and may change with use_frameworks! support.
  CODEGEN_COMPONENTS_PATH="ReactCommon/react/renderer/components"
  CODEGEN_COMPONENTS_OUTPUT_DIR=${CODEGEN_COMPONENTS_OUTPUT_DIR:-"$RN_DIR/$CODEGEN_COMPONENTS_PATH/$CODEGEN_COMPONENTS_LIBRARY_NAME"}

  TEMP_OUTPUT_DIR="$TEMP_DIR/out"
  SCHEMA_FILE="$TEMP_DIR/schema.json"

  if [ -z "$NODE_BINARY" ]; then
    echo "Error: Could not find node. Make sure it is in bash PATH or set the NODE_BINARY environment variable." 1>&2
    exit 1
  fi

  CODEGEN_PATH=$("$NODE_BINARY" -e "console.log(require('path').dirname(require.resolve('react-native-codegen/package.json')))")

  # Special case for running CodeGen from source: build it
  if [ ! -d "$CODEGEN_PATH/lib" ]; then
    describe "Building react-native-codegen package"
    bash "$CODEGEN_PATH/scripts/oss/build.sh"
  fi

  describe "Generating schema from flow types"
  "$NODE_BINARY" "$CODEGEN_PATH/lib/cli/combine/combine-js-to-schema-cli.js" "$SCHEMA_FILE" "$SRCS_DIR"

  describe "Generating native code from schema (iOS)"
  pushd "$RN_DIR" >/dev/null || exit 1
    "$NODE_BINARY" scripts/generate-specs-cli.js ios "$SCHEMA_FILE" "$TEMP_OUTPUT_DIR" "$CODEGEN_MODULES_LIBRARY_NAME"
  popd >/dev/null || exit 1

  describe "Copying output to final directory"
  gmkdir -p "$CODEGEN_COMPONENTS_OUTPUT_DIR" "$CODEGEN_MODULES_OUTPUT_DIR"
  gcp -R "$TEMP_OUTPUT_DIR/$CODEGEN_MODULES_LIBRARY_NAME.h" "$TEMP_OUTPUT_DIR/$CODEGEN_MODULES_LIBRARY_NAME-generated.mm" "$CODEGEN_MODULES_OUTPUT_DIR" || exit 1
  gfind "$TEMP_OUTPUT_DIR" -type f | gxargs gsed -i.bak "s/$CODEGEN_MODULES_LIBRARY_NAME/$CODEGEN_COMPONENTS_LIBRARY_NAME/g" || exit 1
  gfind "$TEMP_OUTPUT_DIR" -type f -not -iname "$CODEGEN_MODULES_LIBRARY_NAME*" -exec cp '{}' "$CODEGEN_COMPONENTS_OUTPUT_DIR/" ';' || exit 1

  echo >&2 'Done.'
}

trap cleanup EXIT
main "$@"

notice that some commands are starting with g like greadlink etc.

if your get invalid identifier error in react-native-xcode.sh then under Build Phases -> Bundle React Native code and images it should be: (notice the double quotes):

set -e
export NODE_BINARY="node ../node_modules/react-native/scripts/react-native-xcode.sh"

use patch-package react-native to patch it (if project is being developed on different machines then they must install the brew packages above)

score 1 · Answer 5 · answered Sep 09 '22 at 20:28

I'm running Xcode 13.4.1
Installed cocoapods using brew install cocoapods (https://brew.sh/index_es)
M2 apple chip
React Native 0.70

Actually after spending a whole lot of time trying different solutions none of them worked except for Giuseppe's answer. I had white spaces in my path "/React Native/exampleProject"

1. Renamed folders/files to remove any white space in the path (creating a fresh project within the fixed path worked with no problems at all)

I didn't even had to execute pod install anymore in the ios folder

Damn man, I used M1 Pro and got the same issue. This answer saves my day man... Thank you — Duy Dau Dzu, Feb 28 '23 at 18:15

score 1 · Answer 6 · answered Dec 11 '22 at 18:50

1

In my case, i had to export the right path to node

in your terminal type which node, copy the path and export it in ios/xcode.env

export NODE_BINARY="copied node path"

answered Dec 11 '22 at 18:50

code salley

307
4
5

score 0 · Answer 7 · answered May 17 '22 at 09:26

0

For me it was just having a space in folder name which was in the path of project folder from root.

answered May 17 '22 at 09:26

Faris Khan

21
3

Shishir Aithal · Answer 8 · 2023-01-02T12:22:43.937

0

Ok, worth trying this. (This usually happens if you had multiple imports or any imports missing)

As soon as we get this error message:

Always scroll up & read the issue if written in that log file. Any issues like syntax error or issue related to your js code. If yes, you can fix that first & re build it.

In my case I had multiple imports of one of the RN components.

edited Jan 02 '23 at 12:22

answered May 18 '22 at 20:10

Shishir Aithal

52
6

score 0 · Answer 9 · answered Jun 22 '22 at 19:01

0

I had to delete the contents of my ~/.bash_profile file.

I don't even use bash, but some other script populated the file and that broke my build. Deleting the contents fixed the build, immediately. Might not work for you, but thought I'd share.

answered Jun 22 '22 at 19:01

SeanMC

1,960
1
22
33

score -1 · Answer 10 · edited Sep 21 '21 at 08:37

-1

Adding $(ARCHS_STANDARD) to Valid Architectures in Build Settings solved it for me

edited Sep 21 '21 at 08:37

Axisnix

2,822
5
19
41

answered Sep 21 '21 at 07:10

Taimoor Awais Khan

1

3

Can you should be more descriptive ? what needs to be added and where ? – Vasanth Oct 18 '21 at 16:34

Xcode 12.4 React native build failed in IOS Showing All Messages Command PhaseScriptExecution failed with a nonzero exit code

10 Answers10

Linked