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.

forwardDebugPort does not work correctly if more than one device / emulator

See original GitHub issue

:realm:forwardDebugPort
error: more than one device/emulator
===========================================================================
WARNING: Failed to automatically forward port 8082.
In order to use Realm in Chrome debugging mode, port 8082 must be forwarded
from localhost to the device or emulator being used to run the application.
You may need to add the appropriate flags to the command that failed:
    adb forward tcp:8082 tcp:8082
===========================================================================

Issue Analytics

State:
Created 7 years ago
Comments:8 (5 by maintainers)

Top GitHub Comments

1reaction

alaziercommented, Apr 12, 2016

We should mention this in the docs.

0reactions

alaziercommented, Mar 31, 2016

Unlike other react-native modules Realm apis are synchronous and are built directly on top of the JS engine. We do this for good performance (we don’t have to copy data for every call) and api simplicity. This is why you are able to access object properties using normal property getters/setters rather than using async callbacks which we thought would be cumbersome and awkward.

To make chrome debugging work with this design we had to build an rpc server that allows us to synchronously forward all api calls so they are run on the device/emulator. This rpc server is what requires port forwarding and is only used when debugging in chrome.