I have a Front end for a mobile app I am working on and I have implemented a basic Login/Signup screen for testing. However, after many hours debugging "why my app's UI is unresponsive on initial startup",

I have noticed that while testing on my android device using Expo Go, the dev menu triggered by pressing m in the terminal prevents the UI from being responsive.

Pressing m to toggle it off fixes the issue and retriggers it when toggled back on.

Anyone know how to prevent the issue permanently? I have been toggling it every time but its annoying to do especially when I fet.

Here is a sample from my terminal where until I toggled the dev menu, even the debug prompts I had would not trigger:

npx expo start -c
>>
Starting project at C:\PATH-INTENTIONALLY OMITTED
Starting Metro Bundler
warning: Bundler cache is empty, rebuilding (this may take a minute)
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
//QR CODE INTENTIONALLY OMITTED
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
› Metro waiting on exp://IP-INTENTIONALLY OMITTED
› Scan the QR code above with Expo Go (Android) or the Camera app (iOS)
› Using Expo Go
› Press s │ switch to development build
› Press a │ open Android
› Press w │ open web
› Press j │ open debugger
› Press r │ reload app
› Press m │ toggle menu
› shift+m │ more tools
› Press o │ open project code in your editor
› Press ? │ show all commands
Logs for your project will appear below. Press Ctrl+C to exit.
Android Bundled 21857ms node_modules\expo\AppEntry.js (1169 modules)
 (NOBRIDGE) LOG  Bridgeless mode is enabled
 (NOBRIDGE) LOG  expo-dev-menu not found or could not be disabled: [Error: Requiring unknown module "undefined". If you are sure the module exists, try restarting Metro. You may also want to run `yarn` or `npm install`.]
 (NOBRIDGE) WARN  [Reanimated] Reduced motion setting is enabled on this device. This warning is visible only in the development mode. Some animations will be disabled by default. You can override the behavior for individual animations, see .
 INFO