React-native: Connection to http://localhost:8081/debugger-proxy?role=client timed out. Are you running node proxy? If you are running on the device, check if you have the right IP address in `RCTWebSocketExecutor.m`.

Created on 23 May 2016  路  15Comments  路  Source: facebook/react-native

I run

react-native init Test1

and run

react-native run-ios simulator

. After 3 secs this show up
screen shot 2016-05-22 at 1 29 18 pm

Connection to http://localhost:8081/debugger-proxy?role=client timed out. Are you running node proxy? If you are running on the device, check if you have the right IP address in RCTWebSocketExecutor.m.

I am running on mac and simulator. I dono if this is a bug? I didnt even change the sample code.

Locked

Most helpful comment

For any future readers, this usually happens when you are running "Debug JS remotely" on multiple devices. Try to turn that off on all simulators/actual devices and rerun the project. It should work.

All 15 comments

Are you running the packager?

npm start

I ran. still happened.
this is my package.json
{
"name": "Test1",
"version": "0.0.1",
"private": true,
"scripts": {
"start": "node node_modules/react-native/local-cli/cli.js start"
},
"dependencies": {
"react": "^15.0.2",
"react-native": "^0.26.1"
}
}

And the packager shows no errors?

what do you mean by "packager show no errors"? sorry i just use react-native for 3 weeks

The packager is the what transform your JS code and runs the debugging proxy... should look something like this:

image

Can you please follow these exact steps to see if you still get the error:

react-native init Test2
cd Test2
react-native run-ios

screen shot 2016-05-23 at 1 25 36 pm

Did you follow the steps above? Looks like you're still trying to run Test1
Do you have remote debugging enabled?

Its works now using another name. hmm...what did it just happen?

Something must have gone wrong during init

If anyone finds this later on, this helps: https://stackoverflow.com/a/43285071/1409779 (an answer to an SO post from the same author as this issue)

+1 This happens to me often while developing/debugging on device. Behavior seems to be inconsistent. The only correlation I can find is if you let the device screen turn off/go to sleep for some variable length of time, it doesn't have to be very long. Sometimes simply restarting the build through Xcode works, sometimes I have to close packager terminal and clean the project.

That being said, I love React/RN and think you're all awesome, keep on keepin' on!

For any future readers, this usually happens when you are running "Debug JS remotely" on multiple devices. Try to turn that off on all simulators/actual devices and rerun the project. It should work.

@srshah19 not really. new project--> running on real device(and no other), in debug mode and debug js remotely . i get this error while loading jsbundle.

@srshah19 Happens to me every 5-30min every day. I have to switch on and then off the airplane mode to be able to connect again with the debugger. This occures even without the debugger, and even if I have the debugger on only one device connected at all (debugger and packager).

@drpiou Wow, I don't want to know why it worked, but it did.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

grabbou picture grabbou  路  3Comments

axelg12 picture axelg12  路  3Comments

ghost picture ghost  路  3Comments

DreySkee picture DreySkee  路  3Comments

aniss picture aniss  路  3Comments