React-native-debugger: Console disappears and remote debugging stops work (0.10.0)

[inferusvv]

React Native Debugger app version: 0.10.0
React Native version: 0.60.5
Platform: iOS, Android
Is real device of platform: Yes/No
Operating System: macOS 10.14.6

I've upgrade RND to 0.10.0 version and now have a problem that console is disappeares and bundle can't be loaded on phone/simulator when remote debugging is on. Issue is everywhere (simulator/real device, android/iOS). It happens time-to-time.

Stuck like this:

[shamilovtim]

Ever since 10.0 I have been having this issue repeatedly. Every 5 minutes I have to restart the debugger.

[rarira]

0.10.1 has the same issue...

[shamilovtim]

This gets you 0.9.14:

brew cask uninstall react-native-debugger

brew cask install https://raw.githubusercontent.com/Homebrew/homebrew-cask/f6db4e3e6c2a773bc2967db5819118299b8a60a1/Casks/react-native-debugger.rb

[CoenWarmer]

Also experiencing this on 0.10.1... Any outlook on a fix?

[mirague]

Same thing here, will downgrade to 0.9.14 thanks @shamilovtim !

[schumannd]

This not only causes the debugger to break, but also causes the app to not load. Major bug.

[flashman2]

Same here...

[minhchienwikipedia]

Same here, downgrade work for me. But I think we should resolve this issue asap!

[dquessenberry]

Same here. RNDebugger freeze about every 10-30 minutes and prevents the simulator from loading. Must quit RNDebugger and restart. This is definitely a major bug and I will downgrade for now. Love this tool though!

[elkinjosetm]

Yep, same here, but I've found that you don't need to restart the whole debugger, just close the inspector, and open it up again. cmd+i to close it, cmd+i to open it up again. It's faster than close the app and then open it up again IMO

[shchu]

Yep, same here, but I've found that you don't need to restart the whole debugger, just close the inspector, and open it up again. cmd+i to close it, cmd+i to open it up again. It's faster than close the app and then open it up again IMO

This work for me, but the hotkey should be cmd + option + i

[MacKentoch]

Appart from helpful workarounds (downgrading or cmd + option + i), is there a blocking point (ex: from react-native, metro...)?

Not bashing at all (I love this tool and thank all people involved) but just want to simply know about.

[inferusvv]

0.10.2. Still exists

[shamilovtim]

Hey just wanted to clarify that anyone can avoid this issue by downgrading to v0.9.14 for now. I listed the instructions to do so up above!

[GunnarAK]

0.10.4. Still exists

[mirague]

How's this looking in 0.10.5? Didn't see any mention in the release notes.

[jean-marc-cp]

I've not had one since upgrading. Don't think that's conclusive though.

[inferusvv]

I am on 0.10.4 and had it only 1 time this week. Very interesting what causes this issue

[bockc]

I'm on 0.10.5 and I can confirm that this issue is still there. I don't know what causes this issue. Nothing's wrong when I'm not debugging, there's no endless loop or whatever, but as soon as I enable the debugger at some point in the code it freezes and causes this issue.

[sorakrisc]

this problem still persist in 0.10.6

[mirague]

This temporary workaround was posted in another similar issue, which is to have the debugger reload itself every N JS-reloads.

Go to Debugger > Open Config File and add these lines:

  // Refresh devtools when doing JS reload every N times. (-1 for disabled)
  // This can effectively avoid possible memory leaks (Like
  // https://github.com/jhen0409/react-native-debugger/issues/405) in devtools.
  timesJSLoadToRefreshDevTools: 5,

[AnthonyWard]

I've created a possible fix & PR here https://github.com/jhen0409/react-native-debugger/pull/531

Basically, electron needs to be updated to at least 7.1.14, as that includes this fix: https://github.com/electron/electron/pull/22338

I'll leave this fork here in case it helps: https://github.com/AnthonyWard/react-native-debugger/tree/v0.10.10-hotfix. To build you can clone, switch to branch v0.10.10-hotfix and do a yarn, yarn build, and yarn pack-linux. I've not tested this on macos yet but it has fixed it on linux for me. :+1:

[ghasemikasra39]

Facing the same issue on 0.11.5. Any solution ?

[MrAlexWeber]

Wanted to report that this issue is persisting in 0.10.7 as well, but I'm willing to live with the workarounds & forks for now 😂

[Asinox]

Well, version 1.1.0 still facing the same issue.

[ghasemikasra39]

Facing the same issue on 0.11.6 on both mac and windows