Remove useTurboModules assertion from ReactHostImpl.getOrCreateStartTask

mdvacca · mdvacca · commit 0ab07a0ac5a2 · 2026-05-19T11:06:38.000-07:00
Summary:
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]

Differential Revision: D105718211
diff --git a/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/runtime/ReactHostImpl.kt b/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/runtime/ReactHostImpl.kt
@@ -856,11 +856,6 @@ public class ReactHostImpl(
           ReactNativeNewArchitectureFeatureFlags.enableBridgelessArchitecture(),
           "enableBridgelessArchitecture FeatureFlag must be set to start ReactNative.",
       )
-
-      Assertions.assertCondition(
-          ReactNativeNewArchitectureFeatureFlags.useTurboModules(),
-          "useTurboModules FeatureFlag must be set to start ReactNative.",
-      )
     }
     if (ReactBuildConfig.UNSTABLE_ENABLE_MINIFY_LEGACY_ARCHITECTURE) {
       Assertions.assertCondition(

Original file line number	Diff line number	Diff line change
`@@ -856,11 +856,6 @@ public class ReactHostImpl(`
`856`	`856`	`ReactNativeNewArchitectureFeatureFlags.enableBridgelessArchitecture(),`
`857`	`857`	`"enableBridgelessArchitecture FeatureFlag must be set to start ReactNative.",`
`858`	`858`	`)`
`859`		`-`
`860`		`- Assertions.assertCondition(`
`861`		`- ReactNativeNewArchitectureFeatureFlags.useTurboModules(),`
`862`		`- "useTurboModules FeatureFlag must be set to start ReactNative.",`
`863`		`- )`
`864`	`859`	`}`
`865`	`860`	`if (ReactBuildConfig.UNSTABLE_ENABLE_MINIFY_LEGACY_ARCHITECTURE) {`
`866`	`861`	`Assertions.assertCondition(`