Skip to content

Commit 26f313b

Browse files
mdvaccameta-codesync[bot]
authored andcommitted
Remove useTurboModules assertion from ReactHostImpl.getOrCreateStartTask (#56927)
Summary: Pull Request resolved: #56927 The `useTurboModules` flag is being deleted; it always returns true on the canary release stage. The DEBUG-gated assertion in `ReactHostImpl.getOrCreateStartTask()` is therefore tautological — remove it. The `enableBridgelessArchitecture` assertion immediately above stays. Behavior is unchanged. Changelog: [Internal] Reviewed By: fkgozali Differential Revision: D105718211 fbshipit-source-id: baca6b599af95247bd632096487eabfc2b9f3e94
1 parent 0f7bd33 commit 26f313b

1 file changed

Lines changed: 0 additions & 5 deletions

File tree

  • packages/react-native/ReactAndroid/src/main/java/com/facebook/react/runtime

packages/react-native/ReactAndroid/src/main/java/com/facebook/react/runtime/ReactHostImpl.kt

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -856,11 +856,6 @@ public class ReactHostImpl(
856856
ReactNativeNewArchitectureFeatureFlags.enableBridgelessArchitecture(),
857857
"enableBridgelessArchitecture FeatureFlag must be set to start ReactNative.",
858858
)
859-
860-
Assertions.assertCondition(
861-
ReactNativeNewArchitectureFeatureFlags.useTurboModules(),
862-
"useTurboModules FeatureFlag must be set to start ReactNative.",
863-
)
864859
}
865860
if (ReactBuildConfig.UNSTABLE_ENABLE_MINIFY_LEGACY_ARCHITECTURE) {
866861
Assertions.assertCondition(

0 commit comments

Comments
 (0)