fix(iOS): Use REACT_NATIVE_PATH env to resolve react native path in Hermes podspec #48574
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
On iOS, the
REACT_NATIVE_PATH
environment variable is set during both the CocoaPods installation process and the app build. Most React Native scripts already rely on this variable or provide a way to specify a custom React Native path (rather than relying on the default node_modules resolution).However, the Hermes podspec currently does not support using
REACT_NATIVE_PATH
to determine the React Native version. This limitation creates issues in scenarios like Expo Go, where React Native is built from a submodule, making Hermes resolve an incorrect React Native versionChangelog:
[IOS] [CHANGED] - Use REACT_NATIVE_PATH env to resolve react native path in Hermes podspec
Test Plan:
Run
pod install
and build