Developer menu in ios simulator will not launch with either cmd + D
or cmd + ctrl + z
things i've checked (in no order) :
cmd + r
works properlywatchman 4.7.0
is installed with brew install watchman
(--HEAD needed libtoolize, in which brew changed to glibtoolize, therefore ./autogen couldn't find it )react-native start --clear-cache
starts successfully, react-native run-ios
builds successfully Other Issues
nw_connection_get_connected_socket_block_invoke 1262 Connection has no connected handler
run indefinitelyreact-native run-ios
outputsCommand failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Debug-iphonesimulator/zelosApp.app/Info.plist Print: Entry, ":CFBundleIdentifier", Does Not ExistCommand failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Debug-iphonesimulator/zelosApp.app/Info.plist Print: Entry, ":CFBundleIdentifier", Does Not Exist
Versions
Any tips / questions would be greatly appreciated!
You can access the developer menu by shaking your device or by selecting "Shake Gesture" inside the Hardware menu in the iOS Simulator. You can also use the ⌘D keyboard shortcut when your app is running in the iOS Simulator, or ⌘M when running in an Android emulator on macOS and Ctrl+M on Windows and Linux.
In App Developer MenuOn Android emulator, you need to press command + M. Debug JS Remotely − Used for activating debugging inside browser developer console. Enable Live Reload − Used for enabling live reloading whenever your code is saved. The debugger will open at localhost:8081/debugger-ui.
Just run react-native log-ios or react-native log-android on the command line inside your project folder. And when you open the Remote JS Debugging, you have to press option+command+i and check the console.
By default, React Native supports ChromeDev tools through its remote debugging capability. When your app is running on Android Emulator, press Ctrl+M on Windows or Cmd+M on Mac to access the in-app developer menu. If it's running on a real device, then you just need to shake your device.
This happens to me too once in a while, and I have not been able to figure out why. However, one workaround is to select Device -> Shake in the simulator menu.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With