Allow opting into RCT_REMOVE_LEGACY_*_INTEROP on iOS OSS (#57892) - #57892
Closed
christophpurrer wants to merge 1 commit into
Closed
Allow opting into RCT_REMOVE_LEGACY_*_INTEROP on iOS OSS (#57892)#57892christophpurrer wants to merge 1 commit into
christophpurrer wants to merge 1 commit into
Conversation
meta-cla
Bot
added
the
CLA Signed
|
@christophpurrer has exported this pull request. If you are a Meta employee, you can view the originating Diff in D115490838. |
Summary: Changelog: [iOS][Added] - Allow consumers to opt into `RCT_REMOVE_LEGACY_MODULE_INTEROP` and `RCT_REMOVE_LEGACY_COMPONENT_INTEROP` from CocoaPods and SwiftPM. Both default to off and will become the default in a future release OSS iOS consumers had no way to set `-DRCT_REMOVE_LEGACY_MODULE_INTEROP=1` and `-DRCT_REMOVE_LEGACY_COMPONENT_INTEROP=1`. This adds that, mirroring the existing `RCT_REMOVE_LEGACY_ARCH` plumbing: - `RCT_REMOVE_LEGACY_MODULE_INTEROP=1` / `RCT_REMOVE_LEGACY_COMPONENT_INTEROP=1` before `pod install` adds the define project-wide via `ReactNativePodsUtils.set_legacy_interop_removal_flags`. - The same variables gate a matching `.define(...)` in `Package.swift`, so a build-from-source React Native compiles without the legacy interop layers too. Both default to `0`. **They will default to `1` in a future release**, at which point the env vars become opt-out. The macros gate declarations in the public `RCTBridge.h` / `RCTBridgeModule.h`, so the define is applied to the whole project rather than to React Native pods alone. When a flag is enabled while using the prebuilt `React.xcframework`, `pod install` warns that only the app-side pruning takes effect. Reviewed By: cipolleschi Differential Revision: D115490838
meta-codesync
Bot
changed the title
christophpurrer
force-pushed
the
export-D115490838
branch
from
August 11, 2026 16:01
ee8cda7 to
4d93824
Compare
|
This pull request has been merged in b933d18. |
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.
Summary:
Changelog: [iOS][Added] - Allow consumers to opt into
RCT_REMOVE_LEGACY_MODULE_INTEROPandRCT_REMOVE_LEGACY_COMPONENT_INTEROPfrom CocoaPods and SwiftPM. Both default to off and will become the default in a future releaseOSS iOS consumers had no way to set
-DRCT_REMOVE_LEGACY_MODULE_INTEROP=1and-DRCT_REMOVE_LEGACY_COMPONENT_INTEROP=1.This adds that, mirroring the existing
RCT_REMOVE_LEGACY_ARCHplumbing:RCT_REMOVE_LEGACY_MODULE_INTEROP=1/RCT_REMOVE_LEGACY_COMPONENT_INTEROP=1beforepod installadds the define project-wide viaReactNativePodsUtils.set_legacy_interop_removal_flags..define(...)inPackage.swift, so abuild-from-source React Native compiles without the legacy interop layers too.
Both default to
0. They will default to1in a future release, at which pointthe env vars become opt-out.
The macros gate declarations in the public
RCTBridge.h/RCTBridgeModule.h, so thedefine is applied to the whole project rather than to React Native pods alone. When a
flag is enabled while using the prebuilt
React.xcframework,pod installwarns thatonly the app-side pruning takes effect.
Reviewed By: cipolleschi
Differential Revision: D115490838