New issue
Advanced search Search tips

Issue 917629 link

Starred by 3 users
Status: Assigned
Owner:
l...@chromium.org
Cc:
chelamcherla@chromium.org
phanindra.mandapaka@chromium.org
santhoshkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android , Windows
Pri: 2
Type: Bug



Sign in to add a comment

inspecting Android tab from chrome://inspect fails with "Not found"

Reported by kservice...@gmail.com, Dec 23 
UserAgent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 OPR/57.0.3098.106

Steps to reproduce the problem:
1.  Connect an Android device with Chrome 71.0.3578.98
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 pop-window  "404 Not Found"

Did this work before? N/A 

Chrome version: 70.0.3538.102  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
Chrome-1.jpg
296 KB View Download

Comment 1 by swarnasree.mukkala@chromium.org, Dec 23

Labels: Needs-Milestone

Comment 2 by phanindra.mandapaka@chromium.org, Dec 26

Cc: phanindra.mandapaka@chromium.org
Labels: Needs-triage-Mobile Triaged-ET
Thanks for filing the issue.

From the above description, this issue is related to Android.
Hence adding the appropriate labels and requesting the team to look into the issue and help in further triaging.

Comment 3 by chelamcherla@chromium.org, Dec 27

Cc: chelamcherla@chromium.org
Labels: Triaged-Mobile Needs-Feedback
@ kservice.profi: Does this happen on every page? Tested this issue using Pixel 2 device connected to Mac both using chrome versions 71.0.3578.99. Could you please provide device details and screencast of the issue.

Thanks!

Comment 4 by kservice...@gmail.com, Dec 28 

Yes, it can happen on any page. Screencast will do later
Project Member

Comment 5 by sheriffbot@chromium.org, Dec 28

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by kservice...@gmail.com, Dec 28 

To sheriffbot@chromium.org I'm sorry, what should I do?

Comment 7 by kservice...@gmail.com, Dec 28 

Can't do screencast yet due to an error "No browsers detected"

Comment 8 by kservice...@gmail.com, Dec 28

Recording #4.mp4
5.0 MB View Download

Comment 9 by santhoshkumar@chromium.org, Jan 8

Cc: santhoshkumar@chromium.org
Labels: TE-NeedsTriageFromHYD
The issue seems to be specific to Android, so forwarding it to Inhouse team for triaging the issue.Hence adding TE-NeedsTriageFromHYD.
Thanks.!

Comment 10 by kservice...@gmail.com, Jan 9 

Thanks!

Comment 11 by jmukthavaram@google.com, Jan 16 (6 days ago)

Labels: OS-Android

Comment 12 by l...@chromium.org, Jan 18 (5 days ago)

Owner: l...@chromium.org
Status: Assigned (was: Unconfirmed)
Thanks for the report.  Based on the versions mentioned:
Desktop Chrome 70.0.3538.102, and Chrome for Android 64.0.3282.137

DevTools cannot guarantee support for remote debugging workflows when the difference in versions is too great.

Could you please see if the following workaround in this other issue works for you?
https://bugs.chromium.org/p/chromium/issues/detail?id=913484#c9
►

Sign in to add a comment