[Expo43] Unable to debug in chrome in bare (iOS)

[TMcLoone]

Summary

After upgrading to expo43 beta and running
EXPO_BETA=1 expo prebuild
"Debug in chrome" locks the app up with the following error:

Error: EISDIR: illegal operation on a directory, read at Object.readSync (fs.js:592:3) at tryReadSync (fs.js:366:20) at Object.readFileSync (fs.js:403:19) at UnableToResolveError.buildCodeFrameMessage (/43Beta/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:347:17) at new UnableToResolveError (/43Beta/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:333:35) at ModuleResolver.resolveDependency (/43Beta/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:211:15) at DependencyGraph.resolveDependency (/43Beta/node_modules/metro/src/node-haste/DependencyGraph.js:413:43) at /43Beta/node_modules/metro/src/lib/transformHelpers.js:317:42 at /43Beta/node_modules/metro/src/Server.js:1471:14 at Generator.next (<anonymous>)

Chrome is set up as per https://reactnative.dev/docs/hermes

This happens in both upgrading a bare expo42 project and a new minimal project (see #14730 )

Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!

bare

What platform(s) does this occur on?

iOS

SDK Version (managed workflow only)

No response

Environment

Expo CLI 4.12.1 environment info:
System:
OS: macOS 11.6
Shell: 5.8 - /bin/zsh
Binaries:
Node: 14.16.1 - ~/.nvm/versions/node/v14.16.1/bin/node
Yarn: 1.22.11 - /usr/local/bin/yarn
npm: 7.16.0 - ~/.nvm/versions/node/v14.16.1/bin/npm
Watchman: 2021.09.06.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 15.0, DriverKit 20.4, macOS 11.3, tvOS 15.0, watchOS 8.0
IDEs:
Android Studio: 4.1 AI-201.8743.12.41.6953283
Xcode: 13.0/13A233 - /usr/bin/xcodebuild
npmPackages:
expo: ~43.0.0-beta.3 => 43.0.0-beta.3
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: 0.64.2 => 0.64.2
react-native-web: 0.17.1 => 0.17.1
npmGlobalPackages:
expo-cli: 4.12.1
Expo Workflow: bare

Reproducible demo or steps to reproduce from a blank project

EXPO_BETA=1 expo init
Select minimal
Delete iOS folder
EXPO_BETA=1 expo prebuild
build, open dev menu and select 'debug in chrome'

Also happens on an upgraded bare expo42 project

[TMcLoone]

Just noticed this in Xcode logs when building

2021-10-13 12:30:14.975131-0400 boop[61817:277687] [native] RCTBridge required dispatch_sync to load RCTDevLoadingView. This may lead to deadlocks 2021-10-13 12:30:16.082105-0400 boop[61817:277706] [javascript] Running "main" with {"rootTag":1,"initialProps":{}} 2021-10-13 12:30:16.394285-0400 boop[61817:277686] [connection] nw_socket_handle_socket_event [C5.1:1] Socket SO_ERROR [61: Connection refused] 2021-10-13 12:30:16.557699-0400 boop[61817:277686] [connection] nw_socket_handle_socket_event [C5.2:1] Socket SO_ERROR [61: Connection refused] 2021-10-13 12:30:16.558432-0400 boop[61817:277690] [connection] nw_connection_get_connected_socket [C5] Client called nw_connection_get_connected_socket on unconnected nw_connection 2021-10-13 12:30:16.558665-0400 boop[61817:277690] TCP Conn 0x600003114370 Failed : error 0:61 [61] 2021-10-13 12:30:17.721101-0400 boop[61817:277706] [javascript] RCTBridge required dispatch_sync to load RCTDevLoadingView. This may lead to deadlocks

And then if I open the dev menu, select 'debug with chrome' it opens the chrome debugging, when opening the inspector the Xcode logs show

2021-10-13 12:31:17.031190-0400 boop[61817:279386] [native] RCTBridge required dispatch_sync to load EXNativeModulesProxy. This may lead to deadlocks

[brentvatne]

latest expo-cli will suppress the EISDIR, which is actually an upstream issue

RCTBridge required dispatch_sync to load RCTDevLoadingView is also an upstream warning: facebook/react-native#16376