react-native
react-native copied to clipboard
Cannot open any debugger
Description
Since a few days I am not able to open any debugger from my React Native app, neither Chrome nor the "react native debugger" app.
When I open the debug menu in my app, I get two tools to open: "Open Debugger" or "Open React DevTools". None of them actually open anything. The only visible effect is a message in the metro console:
info Opening flipper://null/Hermesdebuggerrn?device=React%20Native...when pressing the debugger optioninfo Opening flipper://null/React?device=React%20Native...when pressing the React DevTools option
For what it's worth, I don't even have Flipper installed. I should also add that on iOS, the cmd D or cmd R shortcuts don't work, neither typing "d" in my metro console, I have to go to the Simulator menu and shake the device when I want to open the debug menu.
I already tried to restart the simulator, uninstall and reinstall the app, restart Metro, even restart my computer. I do not have any debugger open in Chrome as well.
When I created a new app from scratch with no other library than react/react-native and their dependencies, I was able to get the "Debug with Chrome" option, and clicking on it actually opened the Chrome debugger. So it seems to be related to my project more than a general issue. The only difference I could spot was that on the clean install, the debugger was labelled by "Running JSI (<some JSI version>)" instead of "Running JSI (HermesRuntime)" for my project.
Version
0.68.2
Output of npx react-native info
System: OS: macOS 12.4 CPU: (8) arm64 Apple M1 Pro Memory: 425.97 MB / 16.00 GB Shell: 5.8.1 - /bin/zsh Binaries: Node: 16.15.0 - /usr/local/bin/node Yarn: 1.22.19 - /opt/homebrew/bin/yarn npm: 8.13.2 - ~/Documents/taketurns-mobile/node_modules/.bin/npm Watchman: 2022.07.04.00 - /opt/homebrew/bin/watchman Managers: CocoaPods: 1.11.3 - /opt/homebrew/bin/pod SDKs: iOS SDK: Platforms: DriverKit 21.4, iOS 15.5, macOS 12.3, tvOS 15.4, watchOS 8.5 Android SDK: API Levels: 28, 30, 31, 32 Build Tools: 29.0.2, 30.0.2, 30.0.3, 31.0.0, 32.0.0, 32.1.0 System Images: android-30 | ARM 64 v8a, android-31 | Google APIs ARM 64 v8a, android-32 | Google APIs ARM 64 v8a Android NDK: Not Found IDEs: Android Studio: 2021.2 AI-212.5712.43.2112.8609683 Xcode: 13.4.1/13F100 - /usr/bin/xcodebuild Languages: Java: 17.0.3 - /opt/homebrew/opt/openjdk@17/bin/javac npmPackages: @react-native-community/cli: Not Found react: 17.0.2 => 17.0.2 react-native: 0.68.2 => 0.68.2 react-native-macos: Not Found npmGlobalPackages: react-native: Not Found
Steps to reproduce
It seems to be only my installation, so N/A
Snack, code example, screenshot, or link to a repository
I was not able to reproduce the bug in a new project, and the project I'm working on is private, so N/A. But I'm willing to provide any required info to debug this situation.
Here is the (not working) debug menu on an iOS 15.5 simulator:

me too. Did you figure it out
me too. Did you figure it out
Sadly no. I’m back to the good old method of console.debug lol
I can be, You need to download this app first
Flipper consists of two parts:
- The desktop app.
- The native mobile SDKs for Android and iOS, the client for JavaScript, or even a third-party client you could implement yourself or find on the web.
+1
I don't want to use Flipper!
As of react native 0.68.5 and iOS 16.1 (macOS 13.0), this issue is still not fixed, and I still didn't get any viable workaround
me too. Who solved the problem
me too. Who solved the problem
same issue on RN 0.72.3 @cortinico Cannot debug anywhere since I use Redux and nested objects are not formatted in Flipper
any news?
@timorss the new react native has an experimental debugger now (standalone version of chrome console):
Start metro:
react-native start --experimental-debugger
Inside the terminal press J
@timorss the new react native has an experimental debugger now (standalone version of chrome console):
Start metro:
react-native start --experimental-debuggerInside the terminal press
J
Is it work for physical device ?
+1 I don't understand why React team leaves a crucial bug to fix it later in future. 😂😂😂
+1 IDK When this issue will be fixed.
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.
This issue was closed because it has been stalled for 7 days with no activity.