change `../node_modules/react-native/packager/react-native-xcode.sh`

change ../node_modules/react-native/packager/react-native-xcode.sh to ../node_modules/react-native/scripts/react-native-xcode.sh

_Originally posted by @AndrewJack in https://github.com/facebook/react-native/issues/14935#issuecomment-314160539_

Seems this is a 0.63.x bug no?

Being that we get this with entirely clean version of 0.63.2 (at least the version I am on), should this not be resolved elsewhere (as opposed to manually). Perhaps, I need to upgrade to another version?

This has gotten 229+ thumbs up, so maybe this actually needs to be resolved somewhere in RN codebase as opposed to just on the comment thread.

It is ok, if I am wrong here. Please include reference, me and at least 229 others have interest in this issue.

[oleksandr-dziuban]

Hi, this PR fixes an issue https://github.com/facebook/react-native/pull/29477

But community didn’t merge it yet

[joebologna]

I’ve had a lot of problems with “Error: cannot find the node binary” because I need to use Node 12 for some things and Node 14 for others. Using nvm to switch works well, but it requires the $SHELL environment to be setup properly. Unfortunately all shells source some basic stuff, then stuff only for “login” or interactive shells. Xcode (for whatever reason) doesn’t pick up the interactive shell stuff, which makes sense, but means when you do which node then run Xcode it will not see which node your are using in your interactive $SHELL.

Mac OS is depreciating BASH in favor of ZSH. If you switch to ZSH as your login shell, things get really icky if you have a .bash_profile and .zprofile.

I suggest making this change to the Bundle React Native code and images section of the .xcodproject generated by react-native:

$SHELL -ls <<EOF
export NODE_BINARY=node
../node_modules/react-native/scripts/react-native-xcode.sh
../node_modules/expo-updates/scripts/create-manifest-ios.sh
EOF

This runs the script as if it were run from your Terminal.