feat(iOS): dynamically resolve react native path in Hermes podspec #46181
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:
This PR modifies hermes-engine.podspec to resolve the path to
react-native
dynamically.In OOT platforms case we often have slightly different versioning, let's say
react-native
is at 0.75.1 andreact-native-visionos
is at 0.75.2. This causes an issue while resolving the prebuilt version of Hermes. We should always get the Hermes tied to thereact-native
package version, not the OOT platform.Changelog:
[IOS] [FIXED] - Resolve Hermes prebuilt version based on react-native packge
Test Plan:
Install pods