react-native: [Chrome Debugging] Can't debug with Chrome devtool

In iOS Simulator press cmd + d twice, console outputs:

Launching Dev Tools...
Failed to run launchChromeDevTools.applescript { [Error: Command failed: /Code/AwesomeProject/node_modules/react-native/packager/launchChromeDevTools.applescript:668:671: script error: Expected class name but found property. (-2741)
] killed: false, code: 1, signal: null }

Simulator outputs:

Environment:

OS X 10.10.2
Chrome 41.0.2272.104 (64-bit)
Xcode 6.2 (6C131e)

About this issue

Original URL
State: closed
Created 9 years ago
Comments: 36 (10 by maintainers)

Links to this issue

android - How do you debug React Native? - Stack Overflow

Commits related to this issue

Fixed name of Chome window, Connects to #297 Summary: Hi! I have the same problem as described here https://github.com/facebook/react-native/issues/297 It could occurs after restarting `packager.sh`... — committed to frantic/react-native by wtfil 9 years ago
Fixed name of Chome window, Connects to #297 Summary: Hi! I have the same problem as described here https://github.com/facebook/react-native/issues/297 It could occurs after restarting `packager.sh`... — committed to facebook/metro by wtfil 9 years ago

Most upvoted comments

It does work with the following steps,

With simulator opened, Press CMD + D once and the node console would output “Launching Dev Tools…” [22:27:49] <START> request:/index.ios.bundle [22:27:50] <START> find dependencies
open chrome http://localhost:8081/debugger-ui (if chrome was not launched in the first step) “Status: Waiting for simulator” will be displayed
CMD + D again on the simulator will display the following message in the console Status: Debugger session #15826 active

kkganesan on Mar 30, 2015

Sometimes I get this error:

Launching Dev Tools...
[Error: not opened]
Error: not opened
    at WebSocket.send (/Users/chris/Projekte/AwesomeProject/node_modules/react-native/node_modules/ws/lib/WebSocket.js:187:16)
    at /Users/chris/Projekte/AwesomeProject/node_modules/react-native/packager/webSocketProxy.js:37:12
    at Array.forEach (native)
    at WebSocket.<anonymous> (/Users/chris/Projekte/AwesomeProject/node_modules/react-native/packager/webSocketProxy.js:36:28)
    at WebSocket.emit (events.js:98:17)
    at Receiver.self._receiver.ontext (/Users/chris/Projekte/AwesomeProject/node_modules/react-native/node_modules/ws/lib/WebSocket.js:697:10)
    at Receiver.opcodes.1.finish (/Users/chris/Projekte/AwesomeProject/node_modules/react-native/node_modules/ws/lib/Receiver.js:397:14)
    at Receiver.expectHandler (/Users/chris/Projekte/AwesomeProject/node_modules/react-native/node_modules/ws/lib/Receiver.js:378:33)
    at Receiver.add (/Users/chris/Projekte/AwesomeProject/node_modules/react-native/node_modules/ws/lib/Receiver.js:93:24)
    at Socket.firstHandler (/Users/chris/Projekte/AwesomeProject/node_modules/react-native/node_modules/ws/lib/WebSocket.js:678:22)

hinzundcode on Mar 28, 2015

I’m getting this after updating to 0.17-beta from 0.12. I also went through the app submission process. Opening up http://localhost:8081/debugger-ui works for me. But I get an error if chrome is simply open.

morenoh149 on Dec 16, 2015

why is this issue closed? i have the same problem OS X 10.9.5 Chrome 41 Xcode 6.2 (6C131e)

i get “Runtime is not ready. Do you have Chrome open?”

mydearxym on May 4, 2015

btw, instead of cmd+d try cmd+ctrl+z - “Enable Debugger”, the former shortcut can’t disable debugging

frantic on Mar 28, 2015