Use devtools-frontend on Chrome for Android, no remote
Reported by
lizher...@gmail.com,
Mar 1 2018
|
|||||||
Issue descriptionSteps to reproduce the problem: It looks like the Dev Tools are not shipped with Chrome for Android. What is the expected behavior? It would be useful to be able to open the DevTools (ex. open the console, inspect HTML elements, debug JS code) on Android without requiring a remote PC. What went wrong? I tried to setup github.com/ChromeDevTools/devtools-frontend to open the Dev Tools in Chrome to debug that same Chrome instance. Th @chrome_devtools_remote abstract unix socket is running (cat /proc/net/unix |grep devtools_remote), but I can't manage to forward it to localhost:9222, which is what the frontend needs. As far as I understand, what should be reproduced on the Android device itself is that simple command : "adb -s <device> forward tcp:9222 localabstract:<service name>". What I tried is : "socat -d tcp-listen:9222,fork abstract-connect:chrome_devtools_remote". Unfortunately, it leads to errors like "connection reset by peer". Did this work before? No Chrome version: 66.0.3356.0 Channel: canary OS Version: Flash Version: Assuming the devtools-frontend could connect to the running Chrome dev tools protocol, would it work ? Or do the Dev Tools require specific libraries not shipped on Android ?
,
Mar 5 2018
This issue seems to be Feature Request. Updating the issue accordingly.
,
Mar 5 2018
,
Mar 9 2018
*** Bulk edit *** Setting Feature Requests as: Untriaged
,
Mar 12 2018
Unfortunately, that's not a supported scenario. We cannot guarantee that DevTools frontend will work correctly on mobile browser. For example, it does not support touch input to the full extent. Is there any reason to not use desktop browser as a host?
,
Mar 13 2018
I've tried the dev tools frontend on Chrome for Android (using ADB forward), it seems to work fine with a mouse and keyboard. Chrome for Android is already well optimized for mouse and keyboard use (e.g. CTRL-L to focus on the URL bar, CTRL-T for a new tab, Ctrl-click to open in a new tab...). That is the use case I had in mind : a tablet connected to a keyboard and mouse, or more importantly the "desktop android" modes that have been appearing lately. , like Samsung's Dex and Huawei's Emui desktop. The latest mobile flagships (e.g. S9) are more powerful than some mid-range laptops. That's more than 50 million devices sold with this potential.
,
Mar 13 2018
As for my problem with the Unix socket, I figured out that it's very logical that this socat command fails : it would introduce a severe security breach as any other application could use that tcp 9222 port to control Chrome's tabs... Hence Chrome must be checking which user is connecting to the socket (which I didn't get first as abstract sockets are reputed to be permissionless). Unfortunately, I have not been able to launch Chrome on Android with the remote debugging port flag (which should launch the TCP server), without rooting the device.
,
Apr 2 2018
,
Dec 5
This is not something we'll fix, due to lack of resources. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by pnangunoori@chromium.org
, Mar 5 2018