Question 131025 in Xcode Question posted in
Whether you're new to Xcode or an experienced developer, our archive has everything you need to know about this integrated development environment (IDE). From basic functionalities to advanced features, our archive covers a wide range of Xcode-related questions and answers. Browse our archive now and find solutions to your Xcode questions, and take your app development skills to the next level

Xcode – React Native – FBReactNativeSpec Command PhaseScriptExecution failed with a nonzero exit code

I am using a MacBook Pro with

  • M1 chip
  • MacOS Big Sur
  • Xcode Version 13.2.1
  • node v14.17.5

I wanted to follow this tutorial to set up a new React Native project called AwesomeProject https://reactnative.dev/docs/environment-setup the section with React Native CLI Quickstart.

When I try to run the app in terminal by typing: npx react-native run-ios
my build fails with the following error:

PhaseScriptExecution [CP-User] Generate Specs /Users/thomashuber/Library/Developer/Xcode/DerivedData/AwesomeProject-aprperxvqrezbfeyvousbagyesvr/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/FBReactNativeSpec.build/Script-5F4C70EF7D90A5A5BDAEB404279F232A.sh (in target ‘FBReactNativeSpec’ from project ‘Pods’)
(1 failure)

When I try to run it in Xcode either on a simulator or on an iPhone device I get the following error in FBReactNativeSpec:

Command PhaseScriptExecution failed with a nonzero exit code

I run it with

/bin/sh -c /Users/thomashuber/Library/Developer/Xcode/DerivedData/AwesomeProject-aprperxvqrezbfeyvousbagyesvr/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/FBReactNativeSpec.build/Script-5F4C70EF7D90A5A5BDAEB404279F232A.sh

I restarted my MacBook, I deleted the project and tried it again. I cleaned the project in Xcode but none of it helps. I suspect that it is due the M1 chip of my MacBook.

Tags:

11

Answers


  1. Chosen as BEST ANSWER
    0

    I managed to get rid of the FBReactNativeSpec error by editing the Project settings.

    Try the following:

    1. In Xcode select your app's project and then select the target.

    2. In Terminal enter the following command to find out the path of your node installation:

    which node

    This should give you a path. Something like:

    /Users/thomashuber/.nvm/versions/node/v16.14.0/bin/node

    1. Copy this path.

    2. In Xcode with the target selected click on Build Phases and open Bundle React Native code and images

    3. Replace NODE_BINARY=node. Instead of node enter the path that you have copied so that it is something like this NODE_BINARY=/Users/thomashuber/.nvm/versions/node/v16.14.0/bin/node

    Replacing node with node path


  2. 0

    Ok, worth trying this.

    2 different solutions :

    1: 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 (like multiple imports in your js files or if you had forgot to import something).
    If yes, you can fix that first & re build it.

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

    if not

    2: got to ‘Keychain access’ in your mac, lock & unlock login and re build it, this may help you.

    And make sure to
    ‘cd ios’ && ‘pod install’
    if you have forgot to do it after installing any of the npm package.

    Login or Signup to reply.
  3. 0
    1. Determine where your node binary is:
        $ which node
    /opt/homebrew/bin/node
    1. Add a fixer function in your Podfile:
        def fix_fb_react_native_spec(installer)
      installer.pods_project.targets.each do |target|
        if target.name == 'FBReactNativeSpec'
          target.build_configurations.each do |config|
            if config.name == 'Debug' or config.name == 'Release'
              config.build_settings['NODE_BINARY'] = '/opt/homebrew/bin/node'
            end
          end
        end
      end
    end
    1. In your postinstall, add fix_fb_react_native_spec(installer) like so:
         post_install do |installer|
        react_native_post_install(installer)
        fix_fb_react_native_spec(installer)
      end

    1. Pod install

    2. Rebuild (ideally with a clean build)

    Login or Signup to reply.
  4. 0

    If you shut down your computer or did a recent upgrade to node or nvm something in the cache folder gets reset and the build fails. The code in the react native node_modules/react-native/scripts/find-node.sh script related to nvm. Following this advice: https://stackoverflow.com/a/70104375/5927929 worked for me with a small change.

    My specs:
    Mac intel chip
    RN 0.68.2
    nvm (0.33.11) && node (v18.3.0) install

    Steps:

    1. nvm unalias default
    2. nvm alias default node
    3. Build in xcode…done
    Login or Signup to reply.
  5. 0

    In my case this error raising due to node path is not set in PATH Variables.
    Try to run below command it will set missing node path in PATH variable and it resolve the error.

    sudo ln -s $(which node) /usr/local/bin/node

    https://reactnative.dev/docs/new-architecture-troubleshooting#:~:text=Command%20PhaseScriptExecution%20failed%20with%20a,libraries%20(FBReactNativeSpec%2C%20rncore).

    Login or Signup to reply.
  6. 0

    In my case:

    • M1 chip
    • MacOS Monterey
    • Xcode Version 13.2.1
    • node v16.6.0
    • react-native 0.69

    I was trying to build the iOS app via terminal under Rossetta. Once I tried to use native M1 terminal – it worked well.

    Go to your applications, right click on the app, get info, check OFF Open using Rossetta

    enter image description here

    Login or Signup to reply.
  7. 0

    In case someone else tried everything mentioned here and in other threads, and it didn’t work, here is what worked for me!

    [!] CocoaPods could not find compatible versions for pod "hermes-engine":
    In snapshot (Podfile.lock):
    hermes-engine (from ../node_modules/react-native/sdks/hermes/hermes-engine.podspec)
    In Podfile:
    hermes-engine (from ../node_modules/react-native/sdks/hermes/hermes-engine.podspec)
    It seems like you’ve changed the version of the dependency hermes-engine and it differs from the version stored in Pods/Local Podspecs.
    You should run pod update hermes-engine --no-repo-update to apply changes made locally.

    But instead of running the command they gave me, I deleted Podfile.lock and the Pods directory, then reran pod install, and the build finally worked!

    Login or Signup to reply.
  8. 0

    Simply delete the FBReactNativeSpec file from the Pods as shown in the image below.enter image description here

    Login or Signup to reply.
  9. 0

    For me anyone of this solutions work because, with Xcode 14.2 and RN0.70.5, there is the following 2 files in ios folder which fixe node version with the path (I don’t know since which version and which one adds this files) :

    1. .xcode.env
    2. .xcode.env.local

    If you are this files inside ios folder just do this (with or without nvm) :

    which node

    And put the patch inside the .xcode.env.local like this :

    export NODE_BINARY="/Users/Blabla/.nvm/versions/node/v16.14.0/bin/node"

    If this files doesn’t exist, try to add it and maybe Xcode will take it into account :

    Inside ios/.xcode.env

    # This `.xcode.env` file is versioned and is used to source the environment
# used when running script phases inside Xcode.
# To customize your local environment, you can create an `.xcode.env.local`
# file that is not versioned.

# NODE_BINARY variable contains the PATH to the node executable.
#
# Customize the NODE_BINARY variable here.
# For example, to use nvm with brew, add the following line
# . "$(brew --prefix nvm)/nvm.sh" --no-use
export NODE_BINARY=$(command -v node)

    Inside ios/.xcode.env.local

    export NODE_BINARY="/Users/Blabla/.nvm/versions/node/v16.14.0/bin/node"
    Login or Signup to reply.
  10. 0

    just run this command

    brew uninstall nvm
    Login or Signup to reply.
  11. 0

    Took me ages to figure this out, my problem was unrelated to any of the other answers.

    The issue was that my project’s full path contained an empty space, so turning

    /Users/radu/Projects/midi control/ua/UaRemoteControl

    into

    /Users/radu/Projects/midi-control/ua/UaRemoteControl

    fixed the build error in XCode.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search