chrome://inspect - Inspecting tab on Android Chromium ToT browser fails (HTTP 404) |
||
Issue descriptionVersions: Linux (Goobuntu) Chrome: Version 52.0.2743.116 (64-bit) Android: Chromium for Android ToT developer builds We're working with tip-of-tree Clank developer builds, and inspecting the rendered results via Chrome on our Goobuntu desktops. Sometime around Tuesday, August 30 (give or take a couple of days), the ability to inspect Chromium tabs on Android devices broke. Visible to 3 developers so far. What steps will reproduce the problem? (1) Build a ToT Chromium build for Android, load, and fire up a tab. (2) Connect the phone to the desktop, and attempt to inspect the remote tab. (3) A window will spawn, indicating "404 Not Found The resource could not be found." No HTML inspection goodness. Let me know what other info I can supply to help...
,
Sep 2 2016
I have the same issue too. I tried with ToT android with stable desktop chrome (52.x) (doesn't work), ToT android with ToT desktop chrome (doesn't work), stable android with stable desktop chrome (works), so I suspect this may be a recent problem. When I was running with ToT desktop chrome, there was an error message for: ERROR:Console(73) "Uncaught TypeError: Cannot read property 'addExtensions' of undefined" which popped up whenever I tried to click inspect on the remote tab
,
Sep 2 2016
The problem is with DevTools frontends in the cloud, which are missing for most recent ToT revisions. Anything older than Sep 1st should be inspectable. We are working on the fix. Sorry for inconvenience!
,
Sep 3 2016
This should be fixed now.
,
Dec 1 2016
|
||
►
Sign in to add a comment |
||
Comment 1 by pfeldman@chromium.org
, Sep 1 2016Status: Assigned (was: Untriaged)