fix(harness): seed Pods/Pods.xcodeproj/project.pbxproj with the new-arch marker#24
Merged
Conversation
…rch marker The community CLI's `installPods` sniffs `ios/Pods/Pods.xcodeproj/project.pbxproj` for `-DRCT_NEW_ARCH_ENABLED=1` to decide what env to pass to `pod install`. On a virgin scaffold that file doesn't exist yet, so the sniffer returns false, the CLI passes `RCT_NEW_ARCH_ENABLED='0'`, and Reanimated 4's podspec assertion aborts the install. `customizeIOS` now pre-seeds the file with the marker substring; CocoaPods overwrites it during the first install with a real Xcode project that carries the same flag, so the sniffer self-sustains on every subsequent rebuild. Bumps `BUILD_FORMAT_VERSION` 6 → 7.
pzuraq
force-pushed
the
separate-bundle-install
branch
from
May 22, 2026 00:55
abd1ff0 to
60e4368
Compare
pzuraq
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fix
bootstrapfailing on iOS for projects that depend onreact-native-reanimated@4. The React Native community CLI'spod installstep was passingRCT_NEW_ARCH_ENABLED='0'on a virgin scaffold because its New Architecture detector relies on a Pods xcodeproj that doesn't exist yet, which Reanimated's podspec asserts against. The harness builder now pre-seeds the file the detector reads, so pod install runs with the New Architecture enabled like the template expects.