Leon Horlings

@Kudo I think we can we merge this now, right? Your PR has been released in 0.74.1 and is also already available in expo https://github.com/expo/expo/pull/28593

Also a somewhat related issue https://github.com/expo/expo/issues/27414 in a different expo package. Both work fine with the old architecture.

Please be aware that expo does not officially support react-native 0.74 yet. Support for 0.74 will most certainly only come out for SDK 51 and not for SDK 50.

> I just realised that my issue is from `expo-dev-menu` not `expo-modules-core` Yes, this is an issue with expo-dev-client and is not related to expo-modules. Removing expo-dev-client fixes the issue....

Had to rebuild because of conflict in a .map file, ready for merge now @aleqsio

Looks like the build failures are unrelated

Setting useFrameworks to static and buildReactNativeFromSource to true in the expo config seems to solve this issue: ``` [ "expo-build-properties", { ios: { useFrameworks: "static", buildReactNativeFromSource: true, }, }, ]...

This only seems to happen on Windows. On Mac this worked fine for me but not on Windows. @byCedric could this be caused by the update to glob@10?

You can patch-package this by changing one line in `node_modules/@expo/config-plugins/build/android/Paths.js` : ```js const filePath = (0, _glob().globSync)(path().join(projectRoot, `android/app/src/main/java/**/${name}.@(java|kt)`))[0]; ``` Into: ```js const filePath = (0, _glob().globSync)(path().join(projectRoot, `android/app/src/main/java/**/${name}.@(java|kt)`).replace(/\\/g, '/'))[0]; ``` globSync...