chrome://inspect can take over the adb communication channel
Reported by
a...@fb.com,
Jan 25 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/602.3.12 (KHTML, like Gecko) Version/10.0.2 Safari/602.3.12 Steps to reproduce the problem: 1. Connect an Android device 2. Issue 'adb kill-server' command 3. Open 'chrome://inspect' 4. Issue 'adb devices' - observe empty device list 5. Close 'chrome://inspect' tab. 6. Issue 'adb kill-server' 7. Issue 'adb devices' - observe device found in list. What is the expected behavior? If chrome://inspect is opened when the adb server is not running, the default Android SDK 'adb devices' should report a connection to a device. What went wrong? adb is unable to connect to a device while Chrome remains open. Did this work before? N/A Chrome version: 55.0.2883.95 (Official Build) (64-bit) Channel: n/a OS Version: OS X 10.12.2 Flash Version: One approach might be to check if adb is in the user's PATH and, if so, run it and use the existing adb communication channel rather than establishing Chrome's own connection.
,
Jan 31 2017
,
Feb 9 2017
Able to reproduce the issue on the latest M-58(58.0.3007.0) on Linux Ubuntu 14.04 as well. Confirming this for more inputs on this. Note: Don't have setup on Windows as of now to confirm the behavior.
,
Feb 13 2017
This works for me on 56.0.2924.76. Are you sure you don't have DevTools open which still takes the usb channel? Could you try to uncheck "Discover USB devices" on chrome://inspect?
,
Feb 14 2017
I reproduced the issue using the steps above with Chrome 56.0.2924.87, with "Discover USB devices" checked. Confirmed the issue does not occur with "Discover USB devices" unchecked.
,
Feb 14 2017
What does discover USB devices actually do? Will it still detect connected devices via adb? El mar., 14 de feb. de 2017 09:23, a… via monorail < monorail+v2.953767718@chromium.org> escribió:
,
Feb 14 2017
re #c6: unchecking "Discover USB devices" forces chrome to use existing adb server. Otherwise, it will try to establish connection itself.
,
Feb 14 2017
Will it automatically start adb in order to find the devices if it's not running? The issue is that this is essentially an implementation detail for many developers and if they aren't explicitly aware of how adb interplays with chrome://inspect they can end up in a state where one or the other doesn't work properly but without any real clue as to why.
,
Oct 4 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by eostroukhov@chromium.org
, Jan 30 2017