-
Notifications
You must be signed in to change notification settings - Fork 24.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
React Native 0.64 is not following NODE_BINARY
env setting in Xcode
#31260
Comments
I tryed manually change NODE_BINARY in generate-specs.sh, but it did not work |
We are seeing the same issue after upgrading to 0.64.0. Always had As a temporary workaround, we are patching the generate-specs.sh as OP suggested, which mitigates the build failure. |
To be honest react-native shouldn't be doing anything with regards to imposing a node version manager on us... it's because of these hacks I can't use Volta |
In XCode, Build Phases -> Bundle React Native code and images, just add
Above This will make Xcode work regardless of your machine using nvm. |
Closing as this version of React Native is several years old. Please re-open a new issue against the latest stable if the issue persists |
solved |
Please provide all the information requested. Issues that do not follow this format are likely to stall.
Description
Previously, I could let RN to find node in non-standard location by specifying
NODE_BINARY
inBundle React Native Code and images
Build phase, but this stopped working after upgrade to RN 0.64 becausegenerate-specs
cannot find node.Same setting was working well on RN 0.63.
React Native version:
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.
export NODE_BINARY=/path/to/node
inBundle React Native Code and images
in Xcode.generate-specs
will complain about node not found and build will fail.Expected Results
The build should success as scripts should follow the
NODE_BINARY
setting.Snack, code example, screenshot, or link to a repository:
PR #30781 stands out as it directly modifies how node is found in
generate-specs.sh
. Manually changeNODE_BINARY
ingenerate-specs.sh
to the path of node works around this problem, but it is dirty.The text was updated successfully, but these errors were encountered: