Yanis f247748adc chore(android): propagate CMake fix to native subprojects ... The withCmakeFix plugin now also modifies the root android/build.gradle via withProjectBuildGradle, iterating over subprojects with plugins.withId('com.android.library') / plugins.withId('com.android.application'). Using plugins.withId (vs subprojects { afterEvaluate {} }) avoids the "Cannot run Project.afterEvaluate when the project is already evaluated" error caused by gradle-plugins (kotlin, expo-gradle-plugin, ...) being evaluated before the closure runs. This unblocks the native CMake build of react-native-fast-tflite, react-native-nitro-modules, react-native-screens, expo-modules-core, etc. on Windows where the path-too-long issue affected subproject .o files. Build verified: BUILD SUCCESSFUL in 15m 17s, 842 tasks, 0 errors. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-01 11:30:55 +02:00
..
withCmakeFix.js	chore(android): propagate CMake fix to native subprojects	2026-05-01 11:30:55 +02:00