New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 867781 link

Starred by 6 users

Issue metadata

Status: Fixed
Owner:
Closed: Sep 19
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Inspecting Android tab from chrome://inspect fails with 404 on recent builds

Reported by drakesky...@gmail.com, Jul 26

Issue description

UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0

Steps to reproduce the problem:
1. Connect an Android device with Chrome 68.03440.70 open
2. Navigate to chrome://inspect.
3. Click "Inspect" on one of the open tabs.

What is the expected behavior?
The tab inspection UI is displayed.

What went wrong?
Only the following is shown: "404 Not Found The resource could not be found."

Did this work before? Yes 67

Chrome version:  Google Inc. Copyright 2018 Google Inc. All rights reserved. Google Chrome	68.0.3440.75 (Official Build) (64-bit) Revision	cf598d63a4f1b9e7cd14f2a8433276b196e3e07d-refs/branch-heads/3440@{#738} OS	Linux JavaScript	V8 6.8.275.24 Flash	30.0.0.134 /home/marcus/.config/google-chrome/PepperFlash/30.0.0.134/libpepflashplayer.so User Agent	Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.75 Safari/537.36 Command Line	/usr/bin/google-chrome-stable --flag-switches-begin --flag-switches-end Executable Path	/opt/google/chrome/google-chrome Profile Path	/home/marcus/.config/google-chrome/Default Variations	c134752e-552119 34a6bf44-ca7d8d80 3095aa95-3f4a17df 7c1bc906-f55a7974 47e5d3db-3d47f4f4 1149accc-3d47f4f4 4dc30737-b8a5ea08 a582a1b8-ad75ce17 44827ee5-3f4a17df 8f1e27f-ca7d8d80 9773d3bd-f23d1dea 9e5c75f1-73498251 f79cb77b-3d47f4f4 4ea303a6-ecbb250e bcc34a89-3f4a17df 2c1d398c-ca7d8d80 2a32876a-ca7d8d80 ff29b1bd-37ef7e17 da460ac8-3f4a17df 4bc337ce-69465896 1354da85-eb933ac9 17507c76-ca7d8d80 494d8760-52325d43 3ac60855-486e2a9c f296190c-22cd16e0 4442aae2-6e3b1976 ed1d377-e1cc0f14 12e17bc5-e1cc0f14 75f0f0a0-a5822863 e2b18481-6754d7b7 e7e71889-e1cc0f14 3a4029d-ca7d8d80 41aa6aaa-da82a76f 94e68624-803f8fc4 8834fcca-ca7d8d80 81c6897f-3f4a17df  Channel: stable
OS Version: 4.15.0-29-generic
Flash Version: Shockwave Flash 30.0 r0

Device is running Android 8.1

This was working prior to the update, and extends to cordova (as Cordova allows use of Chrome as the webview)

This issue mimics the same symptoms as per ticket 760304 though as this issue only became apparent in the recent release this I would assume is likely due to recent changes
 
Screenshot from 2018-07-26 15-16-24.png
20.5 KB View Download
To clarify, the issue is apparent to be linked to the recent release and this has been confirmed as once I reverted the Android version of chrome to 67.0.3396.87 the issue rectified itself
 Issue 867780  has been merged into this issue.
Cc: susan.boorgula@chromium.org
Labels: Needs-Triage-M68 TE-NeedsTriageFromHYD Triaged-ET
drakeskywing@ Thanks for the issue.

As this issue needs to be tested by connecting a Android device, adding 'TE-NeedsTriageFromHYD' label and requesting the appropriate team to look into the issue and help in further triaging.

Thanks..
Cc: krav...@chromium.org cma...@chromium.org
Could someone from 'Clank' team please take a look if it's reproducible on current stable?
 Issue 867923  has been merged into this issue.
Cc: dgozman@chromium.org
Components: -Platform>DevTools Platform>DevTools>Mobile
Owner: pfeldman@chromium.org
Status: Assigned (was: Unconfirmed)
Labels: -Pri-2 Pri-1
I have run into the issue on M69 (stable) on Mac, and on M71 (canary) on Windows. I am trying to remote-debug a chromecast device on the same network.
Owner: dgozman@chromium.org
Status: Fixed (was: Assigned)

Sign in to add a comment