FBReactNativeSpec error after upgrade from 0.63.4 to 0.64.0

See original GitHub issue

Environment

System: OS: macOS 11.2.3 CPU: (8) x64 Intel® Core™ i7-4770HQ CPU @ 2.20GHz Memory: 1.27 GB / 16.00 GB Shell: 5.8 - /usr/local/bin/zsh Binaries: Node: 12.18.0 - ~/.nvm/versions/node/v12.18.0/bin/node Yarn: 1.22.10 - ~/.nvm/versions/node/v12.18.0/bin/yarn npm: 6.14.5 - ~/.nvm/versions/node/v12.18.0/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman Managers: CocoaPods: 1.10.1 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2 Android SDK: API Levels: 28, 29 Build Tools: 19.1.0, 20.0.0, 21.1.2, 22.0.1, 23.0.1, 23.0.2, 23.0.3, 24.0.0, 24.0.1, 24.0.2, 24.0.3, 25.0.0, 25.0.1, 25.0.2, 25.0.3, 26.0.0, 26.0.1, 26.0.2, 26.0.3, 27.0.0, 27.0.1, 27.0.2, 27.0.3, 28.0.0, 28.0.1, 28.0.2, 28.0.3, 29.0.2, 30.0.3 System Images: android-28 | Google APIs Intel x86 Atom Android NDK: Not Found IDEs: Android Studio: 4.1 AI-201.8743.12.41.7042882 Xcode: 12.4/12D4e - /usr/bin/xcodebuild Languages: Java: 1.8.0_281 - /usr/bin/javac npmPackages: @react-native-community/cli: Not Found react: 17.0.1 => 17.0.1 react-native: 0.64.0 => 0.64.0 react-native-macos: Not Found npmGlobalPackages: react-native: Not Found

Things I’ve done to figure out my issue

I used react-native cli to upgrade and the following page to manually changes. https://react-native-community.github.io/upgrade-helper/?from=0.63.4&to=0.64.0

Upgrading version

0.64.0

Description

I’ve faced the following error when I want to start the IOS app with the “react-native run-ios” command. If I start the debug build from XCode, it is started successfully.

/bin/sh -c /Users/keklikc/Library/Developer/Xcode/DerivedData/DataroidMobile-gmjqxfphavicwkcccsennxqbhvuj/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/FBReactNativeSpec.build/Script-0565B84ED1A643A94B66851B97B33BAC.sh nvm is not compatible with the “npm_config_prefix” environment variable: currently set to “/Users/keklikc/.nvm/versions/node/v12.18.0” Run unset npm_config_prefix to unset it. /Users/keklikc/.zshrc: line 83: zstyle: command not found /Users/keklikc/.zshrc: line 84: zstyle: command not found /Users/keklikc/.zshrc: line 85: zstyle: command not found /Users/keklikc/.oh-my-zsh/tools/check_for_upgrade.sh: line 32: syntax error near unexpected token )' /Users/keklikc/.oh-my-zsh/tools/check_for_upgrade.sh: line 32: () {’ /Users/keklikc/.oh-my-zsh/oh-my-zsh.sh: line 21: autoload: command not found /Users/keklikc/.oh-my-zsh/oh-my-zsh.sh: line 39: syntax error near unexpected token (' /Users/keklikc/.oh-my-zsh/oh-my-zsh.sh: line 39: for plugin ($plugins); do’ /Users/keklikc/.zshrc: line 120: autoload: command not found /Users/keklikc/.zshrc: line 129: add-zsh-hook: command not found nvm is not compatible with the “npm_config_prefix” environment variable: currently set to “/Users/keklikc/.nvm/versions/node/v12.18.0” Run unset npm_config_prefix to unset it. Command PhaseScriptExecution failed with a nonzero exit code

warning: The iOS Simulator deployment target ‘IPHONEOS_DEPLOYMENT_TARGET’ is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.4.99. (in target ‘Flipper-Glog’ from project ‘Pods’) warning: The iOS Simulator deployment target ‘IPHONEOS_DEPLOYMENT_TARGET’ is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.4.99. (in target ‘boost-for-react-native’ from project ‘Pods’) warning: The iOS Simulator deployment target ‘IPHONEOS_DEPLOYMENT_TARGET’ is set to 8.4, but the range of supported deployment target versions is 9.0 to 14.4.99. (in target ‘Flipper-PeerTalk’ from project ‘Pods’) warning: The iOS Simulator deployment target ‘IPHONEOS_DEPLOYMENT_TARGET’ is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.4.99. (in target ‘YogaKit’ from project ‘Pods’) warning: no rule to process file ‘/Users/keklikc/Projects/Dataroid-MobileApp/ios/Pods/Flipper-RSocket/rsocket/README.md’ of type ‘net.daringfireball.markdown’ for architecture ‘x86_64’ (in target ‘Flipper-RSocket’ from project ‘Pods’) warning: no rule to process file ‘/Users/keklikc/Projects/Dataroid-MobileApp/ios/Pods/Flipper-RSocket/rsocket/benchmarks/CMakeLists.txt’ of type ‘text’ for architecture ‘x86_64’ (in target ‘Flipper-RSocket’ from project ‘Pods’) warning: no rule to process file ‘/Users/keklikc/Projects/Dataroid-MobileApp/ios/Pods/Flipper-RSocket/rsocket/benchmarks/README.md’ of type ‘net.daringfireball.markdown’ for architecture ‘x86_64’ (in target ‘Flipper-RSocket’ from project ‘Pods’) warning: The iOS Simulator deployment target ‘IPHONEOS_DEPLOYMENT_TARGET’ is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.4.99. (in target ‘Flipper-DoubleConversion’ from project ‘Pods’)

** BUILD FAILED **

The following build commands failed: PhaseScriptExecution [CP-User]\ Generate\ Specs /Users/keklikc/Library/Developer/Xcode/DerivedData/DataroidMobile-gmjqxfphavicwkcccsennxqbhvuj/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/FBReactNativeSpec.build/Script-0565B84ED1A643A94B66851B97B33BAC.sh (1 failure)

Reproducible demo

Upgrade from 0.63.4 to 0.64.0 then execute react-native run-ios

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:162
  • Comments:170 (1 by maintainers)

github_iconTop GitHub Comments

125reactions
mzucommented, Mar 25, 2021

In case anyone wants to try a temporary fix that worked for me: I ended up commenting all lines inside node_modules/react-native/scripts/find-node.sh. It seems as if my node environment didn’t agree with this script. I could build and run my project on an actual device afterwards without any further issues.

89reactions
SpawnAtiscommented, Mar 24, 2021

I was able to resolve this problem with node by the following commands:

  1. brew uninstall yarn
  2. npm install --global yarn
Read more comments on GitHub >

github_iconTop Results From Across the Web

Upgrading to React Native 0.64.0 and their build fails.
Trying to build after the upgrade I would receive this error. The following build commands failed: PhaseScriptExecution [CP-User]\ Generate\ ...
Read more >
FBReactNativeSpec.h error after upgrading from 0.68.x to 0.69.0
I think this is caused by some pods in your react-native project that are not the latest version and as a result some...
Read more >
React Native Upgrade Helper
When upgrading, you should replace them with your actual project's name. You can also provide your app name by clicking the settings icon...
Read more >
Upgrading to new versions - React Native
The upgrade command works on top of Git by using git apply with 3-way merge, therefore it's required to use Git in order...
Read more >
command phasescriptexecution failed with a nonzero exit ...
I managed to get rid of the FBReactNativeSpec error by editing the Project ... npx react-native upgrade and resolve conflicts if any; After...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found