New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 792325 link

Starred by 2 users
Status: Assigned
Owner:
█ lushnikov@chromium.org
Last visit 28 days ago
Cc:
dgozman@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

DevTools: failing to reconnect devtools to remote device

Project Member Reported by lushnikov@chromium.org, Dec 6 2017 
As reported in  crbug.com/745245 :

Another problem I've noticed is that when I disconnect my device (as in pressing the lock button) and then unlock my device and head back to Google Chrome and I click the Reconnect DevTools when I see my device is connected & visible in DevTools it just gives me a blank DevTools page.

>pls find screenshot link attached
http://i.imgur.com/NRYgzoS.png

Comment 1 by m...@manichord.com, Jul 16 

This is also a really big time-sink annoyance when using Chrome Devtools as a front end for other targets that implement the Chrome Devtools protocol such as Stetho (https://github.com/facebook/stetho), which once disconnected cannot reconnect without going back to the Chrome tab with "chrome://inspect" and again clicking on the remote target (documented here: https://github.com/facebook/stetho/issues/194)

It would be nice if DevTools could either automatically reconnect or even just provide a UI control (eg. button) in the DevTools window to reconnect instead of requiring the above process. According to Paul Irishes post: (https://medium.com/@paul_irish/debugging-node-js-nightlies-with-chrome-devtools-7c4a1b95ae27) the stand alone window mode for NodeJS does have this auto-reconnect functionality.
►

Sign in to add a comment