Chrome debugging fails in RN using Realm
See original GitHub issueWhen 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
The app keeps running on the device.
When trying to reload the app, it loads forever (the indicator keeps spinning):
Unlike #491 there are no get_property
requests listed in dev tools:
These errors began when I started to use Realm in my app. Everything works fine except for Chrome Debugging.
Issue Analytics
- State:
- Created 7 years ago
- Comments:17 (8 by maintainers)
Top Results From Across the Web
Realm Integration Breaks React Native Debugger - MongoDB
When attaching the react native debugger to our project we receive the error “Realm is not defined”, which also causes application crashes. This ......
Read more >Using Realm and Remote Debugging fails on android
Easy fix is to goto node_modules/realm/lib/browser/rpc.js and replace line 216 with let url = 'http://127.0.0.1:8083/' + command;.
Read more >realm - npm
Issues with debugging. Some users have reported the Chrome debugging being too slow to use after integrating Realm into their react-native ...
Read more >realm | Yarn - Package Manager
It implies that we envision a near future where the Chrome debugging will be removed, and we currently don't invest much in its...
Read more >Known Issues - Ivanti
Symptom: On connecting to a PCS with R12, a Console Window flashes briefly, ... Symptom: ESAP download fails through Pulse Client when host...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub 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.