Please provide more information.
Closing, since this is an already discussed issue about debugging on device.
I just got that exact error whilst debugging in React-native for Android. What was the solution/related issue ?
Ok i found out it was because i was offline. (Was testing offline mode for my app).
I'm getting this error while trying to run on my iOS device. Any solution on how to get around this?
More info: I only get this when I try to debug js remotely.
Here is a stack overflow link that also seems to have the same issue I'm having
Using:
Environment:
OS: macOS High Sierra 10.13.2
Node: 8.9.3
Yarn: 1.3.2
npm: 5.6.0
Watchman: Not Found
Xcode: Xcode 9.2 Build version 9C40b
Android Studio: Not Found
Packages: (wanted => installed)
react: 16.0.0 => 16.2.0
react-native: ^0.51.0 => 0.52.0
Same issue running in android / linux.
Using:
"react-native": "0.52.0",
"realm": "^2.2.4"
I Tried open 2 terminals:
1) in separate terminal
project-dir$/ react-native start --reset-cache --port=8082
2) after in project vscode
project-dir$/ react-native run-android --port=8082
3) in device, menu Dev Settings / Debug server host & port for device => localhost:8082
Result: project open ok, debug ok (http://localhost:8082/debugger-ui/), but When I call the function in the database, issue appears.
Need some more configuration to work with realm and debug ?
@arshbot Any solution?
@arshbot I'm getting the same error , Have you solved this problem?
Also having the same issue, with internet off.
What a suck work!It exists for 2 years without fixing.
In my case, this error was occured in the following case:
Trying to debug the react native app used realm.
Solution worked for me:
adb forward tcp:8083 tcp:8083In my case, this error was occured in the following case:
Trying to debug the react native app used _realm_.
Solution worked for me:
- connect the device and system in a same network.
- Run this command
adb forward tcp:8083 tcp:8083
But i want to run app without ethernet connection?
same here with iPhone, I find that it only happens on real device with Chrome Developer Tools. So I have to use simulator, or use real device with Safari Developer Tools 😫
update:
It works now.
Here is something I have found ,I am not quite sure if it's right ,but hope it's still useful in some ways.I think this issue is related to your local network, when you run your app on a real device and debug it with Chrome Developer Tools, the debugger will try to make a request like 'http://yourIphonIP:8083/create_session', but this request fails somehow and then this error occurs. I know it's very weird, because if you disable Chrome Developer Tools, everything is fine. but trust me this error is related to your wifi network in some way ,so the debugger can not connect to your device....😅🤦♂️
So I restart my wifi router, change ip of my mac and iPhone, and then the error disappeared.
Can someone tell me please what is the status with this? we are using react native and realm and cannot use chrome debugger on iOS. Constantly getting Must first create RPC session with a valid host.
Can someone tell me please what is the status with this? we are using react native and realm and cannot use chrome debugger on iOS. Constantly getting Must first create RPC session with a valid host.
Agree, this is really bad.
Basic debugging on device and in emulator should be a top priority for development.
Same issue here.. I am trying do test my app on offline conditions using a real device
Same here
Kindly fix out this issue !
What suck work! It exists for 3years without fixing.
+1
@ronyv89 Could you please comment with how you solved it, or the discussion you found?
We appreciate all of your patience with this issue.
We are working on an improved React Native debugging experience, which will be released soon on the v10 branch.
For whoever gets to this issue from Google - this issue is more actively tracked in this ticket:
https://github.com/realm/realm-js/issues/3358
"realm": "^10.0.1"
Same problem
In my last project i used "realm": "^6.0.4"
I downgrade current to 6.0.4 version. It is not good solution, but it work for my.
"realm": "^10.0.1"
Same problem
Most helpful comment
Ok i found out it was because i was offline. (Was testing offline mode for my app).