Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Still Unable To Use Remote JS Debugging For Android Emulator

See original GitHub issue

When I try to enable Remote JS Debugging I am encountering “Error: Failed to load ‘http://localhost:8082/create_session’”.

It seems like this issue has been covered several times (#276, #284) and I’m wondering if there is a fix in the works, or one I haven’t yet discovered.

I remain unable to effectively debug in an Android emulator. I have just updated to Realm v0.15.0 and the issue persists. I find that if I run the suggested command adb reverse tcp:8081 tcp:8081 followed by adb forward tcp:8082 tcp:8082 that this will allow me to load my app and continue working, but as soon as I hit an error or reload I’m back to square one with the same error message and have to run the two adb commands again.

If sharing information about my project or process will help resolve this issue please let me know and I will gladly pass it along.

Issue Analytics

State:
Created 7 years ago
Reactions:7
Comments:7 (2 by maintainers)

Top GitHub Comments

1reaction

esuttoncommented, Dec 5, 2017

Is adb logcat the * only * way to debug if your app uses realm-js ?

I cannot use Chrome debugger at all. I use a mixture of Genymotion and real devices for Android development.

How to Debug Your App If You Use Realm

Stare at your white screen emulator waiting for app load. ( It literally takes 5 minutes )
Make quick code change
Press Reload to test, go to step 1 and wait 5 minutes, repeat

		"react": "^16.0.0",
		"react-native": "^0.50.3",
		"realm": "^2.0.12",

Work-Around:

None.

react-native-debugger still takes 5 minutes to load.

However, you can watch thousands of ~50 millisecond getProperty calls scroll by in the Network tab while you wait to test your code change.

1reaction

aloifoliacommented, Oct 15, 2017

Similar here. I am using

react 16.0.0
react-native 0.49.2
realm 1.13.0

As soon as I start the JS debugger in genymotion, the promise generated by Realm.open does not succeed nor throw an error. So basically, nothing happens. Has this ever worked flawlessly?

I have two options now:

create my own Realm mock which will be used whenever I want to debug something
ditch Realm altogether which seems to be a viable option, given the time I have been wasting with Realm’s issues when doing basic tasks