Debugger Without Chrome

Expo SDK
1

Hi, I’m using exp on c9.io and I can’t run the debugger. Can I run the debugger through the tunnel instead of local host?

[exp] Launching Dev Tools…
[exp] Google Chrome exited with error: { Error: spawn google-chrome ENOENT
[exp] at exports._errnoException (util.js:1034:11)
[exp] at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
[exp] at onErrorNT (internal/child_process.js:367:16)
[exp] at _combinedTickCallback (internal/process/next_tick.js:80:11)
[exp] at process._tickCallback (internal/process/next_tick.js:104:9)
[exp] code: ‘ENOENT’,
[exp] errno: ‘ENOENT’,
[exp] syscall: ‘spawn google-chrome’,
[exp] path: ‘google-chrome’,
[exp] spawnargs: [ ‘http://localhost:19001/debugger-ui’ ] }

Thanks

2

Hi @ifr33m4n

You should be able to run through a service like this one http://remotedev.io/ to get dev tools going. I’m not sure if you can get the chrome dev tools going through a service like this however.

1 Like
3

The debugger tried to set up a websocket connection to a packager. In you case, looks like the packager is running on the cloud. When Chrome opens, it may try to connect to localhost, which does not exist. You could simply load up chrome, use the debugger to look at debugger-ui.js and make that connection to the place where the packager is running.