Issue metadata
Sign in to add a comment
|
Remote device debuggin -> inspect produce HTTP/1.1 404 Not Found
Reported by
vzyatko...@gmail.com,
Jun 17 2018
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Firefox/60.0 Steps to reproduce the problem: 1. Setup remote debuggin macOS and android8 2. Open page and click inspect 3. What is the expected behavior? Expect to see inspect mode What went wrong? After click inspect in opened window popUp i see "HTTP/1.1 404 Not Found" (ckeck screenshot). Issue became recently probably as mac updated version sierra. Did this work before? Yes Chrome version: Version 69.0.3462.0 (Official Build) canary (64-bit) Channel: canary OS Version: 10.12.6 Flash Version: Shockwave Flash 28.0 r0
,
Jun 17 2018
This problem is absent if i am using stable version chrome 67. Issue is only for canary. But main problem that i need canary for inspect some additional features like hitTest API for WebXR
,
Jun 17 2018
,
Jun 18 2018
As this issue requires android 8 to triage adding TE-NeedsTriageFromHYD label for further triaging from Inhouse team. Could someone from Inhouse please have a look at this issue. Thanks!
,
Jun 19 2018
,
Jun 19 2018
vzyatkov06@ -- Thanks for reporting this issue. Tested on latest Canary #69.0.3465.0 using Mac 10.13.3, Windows 10 and Debian Rodete and was not able to reproduce the issue and was able to connect to the device properly. Attached the screen cast for reference. Could you please update your Canary to latest version and please share the device details including the OS and build details where the issue is reproduced. Also, please share the URL details if it is specific to any URL. Removing 'Needs-Bisect' label as issue is not reproduced. Thanks in advance!
,
Jun 23 2018
Since the issue is no longer reproducible, it sounds like Chrome Canary got updated and fixed the issue. Speculatively closing this, feel free to re-open if it still reproduces.
,
Jul 17
We're getting this same 404 trying to use remote debugging with Canary too. On the desktop we've seen this using Mac OS X 10_13_4: - Chrome Canary 69.0.3493.0 (Official Build) canary (64-bit) and - Chrome Canary 67.0.3396.99 (Official Build) (64-bit) and on Ubuntu Linux (Xenial 16.04) - Google Chrome (stable) 67.0.3396.99 (Official Build) (64-bit) On the mobile side we've seen this using: - Samsung Galaxy S7 (69.0.3492.0 (Official Build) canary (32-bit) on Android 8.0.0: SM-G930F Build/R16NW) - Google Pixel (first edition) in Chrome Canary (69.0.3492.0 (Official Build) canary (32-bit) on Android 8.1.0: Pixel XL Build/OPM4.171019.021.P1) Let us know if you need more info. Can we re-open this please?
,
Jul 18
This has started happening in Chrome Dev now too. It was working fine on Android 8.1.0: Pixel XL Build/OPM4.171019.021.P1) in version 69.0.3475.0 Browser auto-updated to 69.0.3493.4 and now it's stopped working and just throws 404 8(
,
Jul 20
Re-opening based on the above reports.
,
Jul 24
I do see the error on about:inspect when connecting to canary (android 70.0.3498.0) from mac (67.0.3396.99), but inspect fallback works. When I connect from canary mac (70.0.3498.0) to the phone, there is no inspect fallback link, and I still get the 404. I opened the inspect window in debug tools, and there were 2 loaded files - "devtools_compatibility.js", with javascript in it, and inspector.html?remoteFrontend=true&dockSide=undocked, which just contains "HTTP/1.1 404 Not Found".
,
Jul 27
After hoping it would be available in beta and stable, I downloaded those versions. Unfortunately the same happens in both of those versions. Same issues as mentioned by billorr. Reproduced with latest versions of both channels on up-to-date W10 combined with an up-to-date Nexus6P with Chrome Dev on my mobile.
,
Jul 27
Same issue appears with Edge for android (chromium based)
,
Aug 2
,
Sep 13
I am running into this issue. I am trying to debug a chromecast device on the same network. I ran into the issue both on a stable build on Mac (M69), and a canary build on Windows (M71)
,
Dec 3
Even i am facing this issue, whether anybody resolved it ? |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by vzyatko...@gmail.com
, Jun 17 2018