Issue metadata
Sign in to add a comment
|
chrome-devtools inspect tab returns 404 |
||||||||||||||||||||||
Issue descriptionChrome host Version: 59.0.3071.115 or 61.0.3160.0 OS: Linux Chrome target Version: 61.0.3160.0 OS: Android 5.1.1 What steps will reproduce the problem? (1) Setup android device USB debugging and open chrome (2) On host machine, navigate to chrome://inspect/#devices (3) inspect any of the tags What is the expected result? Remote inspection/debbuging starts. What happens instead? A page with: "404 Not Found The resource could not be found." Appears instead. The URL for the new window is: chrome-devtools://devtools/remote/serve_rev/@f240682bd1432178a36f03429fef24b05d0d8c99/inspector.html?remoteFrontend=true&dockSide=undocked
,
Jul 27 2017
Yep, it usually takes up to a day for DevTools frontend to propagate to the cloud.
,
Jul 28 2017
I'm also affected by this. I just built 60.0.3112.78, which is 4 days old and was promoted to stable. https://chromium.googlesource.com/chromium/src/+/a06489456eeba3939f2f058a4e5bd6178e7b3bb9 I'm not sure what to do now.
,
Jul 28 2017
(I notice it's still beta for Android.) |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by caseq@chromium.org
, Jul 20 2017Labels: Needs-Feedback