Error when trying to debug from device

[vitch]

After following the instructions to run my app on a device I still got an error when I shook the device and tried to enter debug mode:

[RCTWebSocketExecutor.m:108] WebSocket connection failed with error Error Domain=NSPOSIXErrorDomain Code=61 "The operation couldn’t be completed. Connection refused"
2015-04-16 16:35:58.255 [error][tid:main][RCTWebSocketExecutor.m:50] Connection to http://localhost:8081/debugger-proxy timed out. Are you running node proxy? If you are running on the device check if you have the right IP address on `RCTWebSocketExecutor.m` file.

With help from @vjeux on IRC we got it down to RCTWebSocketExecutor.m#L33 where localhost is hardcoded.

Hardcoding my current IP address in there fixed the issue for me but the actual fix will obviously involve passing through the value of jsCodeLocation.

[vjeux]

There are two other urls that are suspiciously hardcoding localhost:

react-native/React/React.xcodeproj/project.pbxproj

Line 465 in 862d9fb

shellScript = "if nc -w 5 -z localhost 8081 ; then\n if ! curl -s \"http://localhost:8081/status\" | grep -q \"packager-status:running\" ; then\n echo \"Port 8081 already in use, packager is either not running or not running correctly\"\n exit 2\n fi\nelse\n open $SRCROOT/../packager/launchPackager.command || echo \"Can't start packager automatically\"\nfi";

react-native/React/Base/RCTRedBox.m

Line 85 in 862d9fb

request.URL = [NSURL URLWithString:@"http://localhost:8081/open-stack-frame"];

cc @frantic

[kiddkai]

This works, thanks..

[jtremback]

Is there some solution to this? I've written a script that switches these by finding and replacing but it seems janky.

[brentvatne]

@jtremback - this is being tracked in #1429 now, PR welcome!

[jtremback]

@brentvatne wasn't there another PR where someone had written objC code to switch the IP?

[brentvatne]

@jtremback - hmm, it sounds vaguely familiar but having looked through several hundred issues in the last few days I'm having a hard time remembering exactly, if you find it let me know

[aleclarson]

#6362 and #6345 both have a go at fixing this issue