@
@joaovfcanuto
I'm using macOS for running the expo dev server and connecting to it via SSH in vscode on a windows machine to code the app.
Everything works fine as far as building, coding and running, the only problem I had so far was debugging.
Pressing J on the cli to launch the debugger only launches the debugger on the host machine and that is to be expected, but expo-cli seems to block connections NOT coming from the host machine when It comes to debugging, specifically these two lines
https://github.com/expo/expo/blob/cb7c6ddfef26b492d5fe772e5152fdee996c5e0c/packages/%40expo/cli/src/start/server/metro/debugging/createDebugMiddleware.ts#L67
https://github.com/expo/expo/blob/cb7c6ddfef26b492d5fe772e5152fdee996c5e0c/packages/%40expo/cli/src/start/server/metro/debugging/createDebugMiddleware.ts#L77
By changing them to not terminate the socket connection when it's not a host machine and returning the middleware function respectively I can reach http://macOS-IP:8081/json, get the debug metadata, install the @react-native/debugger-shell package on my windows machine and launch the debugger from there using the data I got from the metadata json.
I created a separate windows application just to list out the devices and launch the debugger from that metadata using this method.
Since all of this is hardcoded into the expo-cli, I was wondering if there could be a option to either allow external connections to get the json data in order to launch the standalone debugger or change both expo-cli to allow for that option and the standalone debugger frontend to select which app and device to debug.
I believe this was changed somewhere down the line very recently, since I recently just upgraded the expo and react native versions of the app I'm working on from a older version to the newest expo version and I don't think the expo-cli was blocking external connections before.