Geek Answers Handbook

Is debugging from the built-in Chrome from the device broken? (Runtime is not ready for debugging)

Can anyone suggest anything to check that debugging Chrome debugging on the device? Debugging Chrome perfectly debugs the iOS simulator.

Debugging Chrome from iOS devices worked fine for over a month, until it stopped working a week ago.

I spent several days trying to start debugging Chrome again. I even started with the new AwesomeProject. Bad luck.

Does the Chrome debugging URL remain the same for debugging both the device and the simulators?

enter image description here

Using OS X 10.11.3, Xcode 7.3, iOS 9.3, and 0.22 native response

  • MacBook WiFi: 173.17.29.213
  • iPad WiFi: 173.17.29.77
  • I can ping an iPad from a MacBook.
  • I can run AwesomeProject on the iPad and activate a reboot.
  • I can debug fine in simulator when jsCodeLocation is set to localhost
  • I killed Chrome and restarted it by opening http: // localhost: 8081 / debugger-ui
  • React Packager works
  • I can set Xcode breakpoints

File: AppDelegate.m

jsCodeLocation = [NSURL URLWithString:@"http://173.17.29.213:8081/index.ios.bundle?platform=ios&dev=true"];

The Xcode debug console appears:

 2016-03-31 08:02:12.286 [error][tid:com.facebook.react.RCTBridgeQueue][RCTWebSocketExecutor.m:85] Runtime is not ready for debugging. - Make sure Packager server is running. - Make sure Chrome is running and not paused on a breakpoint or exception and try reloading again. 2016-03-31 08:02:12.319 [error][tid:main][RCTWebSocketExecutor.m:132] WebSocket connection failed with error Error Domain=NSPOSIXErrorDomain Code=61 "Connection refused" 2016-03-31 08:02:12.513 [fatal][tid:main] Runtime is not ready for debugging. Make sure Packager server is running. 2016-03-31 08:02:36.032 [error][tid:main][RCTWebSocketExecutor.m:132] WebSocket connection failed with error Error Domain=NSPOSIXErrorDomain Code=61 "Connection refused" 2016-03-31 08:02:36.032 [error][tid:com.facebook.react.RCTBridgeQueue][RCTWebSocketExecutor.m:85] Runtime is not ready for debugging. - Make sure Packager server is running. - Make sure Chrome is running and not paused on a breakpoint or exception and try reloading again. 2016-03-31 08:02:36.707 [fatal][tid:main] Runtime is not ready for debugging. Make sure Packager server is running.

File: package.json

 { "name": "AwesomeProject", "version": "0.0.1", "private": true, "scripts": { "start": "node node_modules/react-native/local-cli/cli.js start" }, "dependencies": { "react": "^0.14.8", "react-native": "^0.22.2" } }
+6
source share
1 answer

You are close, one more step and works for me at the moment when you are faced with a specific situation:

"Debugging on a real device:

On iOS, open the RCTWebSocketExecutor.m file and change localhost to the IP address of your computer. Shake the device to open the development menu with the ability to start debugging. [one] "

[1] https://facebook.imtqy.com/react-native/docs/debugging.html

+14
source

More articles:


All Articles