From 28e1ca98737014a9a1735789b3fb817255ffdfdf Mon Sep 17 00:00:00 2001 From: gabrieldonadel Date: Wed, 26 Apr 2023 09:30:20 -0700 Subject: [PATCH] Remove remote debugging from dev menu (#36754) Summary: This PR proposes the removal of the ability to use remote JS debugging (a.k.a Chrome Debugging) from the DevMenu. This change has been suggested previously on the contributor's Discord server and it is motivated by the fact that generally speaking, this feature does not work with the new architecture and most of the popular modules these days. The remote JS debugging is basically broken if you use Turbo Modules, Fabric, or sync native module calls. People tend to assume that if something is part of the dev tools UI, it is going to work reliably. However, when it comes to remote debugging using JSC that's increasingly unlikely to be the case. Having it continue to exist as an option has created some confusion, or at least that's what we've seen within the Expo community. ### How to manually enable remote debugging If your project depends on remote debugging, you can still enable it manually through the `NativeDevSettings`. E.g. ```jsx import NativeDevSettings from 'react-native/Libraries/NativeModules/specs/NativeDevSettings'; export default function App() { return (