realm-js: Chrome debugging fails in RN using Realm

When enabling Chrome Debugging in the React Native app running on a real device, the Chrome Debugging Tab opens and after some seconds, this error appears debugerror The app keeps running on the device. When trying to reload the app, it loads forever (the indicator keeps spinning): debugerror2 Unlike #491 there are no get_property requests listed in dev tools: debugerror3

These errors began when I started to use Realm in my app. Everything works fine except for Chrome Debugging.

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 17 (8 by maintainers)

Most upvoted comments

I am closing the issue as we have in v10.x made many changes to our Chrome debugger support.

I think we simply have issues with chrome debug mode when running on device. Hopefully you can debug your app using the emulator/genymotion until we are able to properly support this. In my experience genymotion is much faster/a better dev experience.

I could be that port forwarding isn’t working. This is supposed to happen automatically but could happen if you have multiple devices. Can you try running these commands to see if they make a difference?

adb reverse tcp:8081 tcp:8081
adb forward tcp:8082 tcp:8082