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

Issue 853851 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Dev Tools bugs out completely when using "inspect devices" with an android app API v23 or older

Reported by d...@altshiftdev.com, Jun 18 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36

Steps to reproduce the problem:
1. Launch an android app in dev mode (I used a cordova app in dev mode) might also work with the chrome browser app on the phone.
2. Go here: chrome://inspect/#devices
3. Try to interact with devtools, it should be glitching out like in the streamable video link provided.

What is the expected behavior?

What went wrong?
I've isolated the behaviour to android remote debugging and it seems to only affect API versions 23 or older. Using android studio emulators.

Android 24+ (7.0.0 +) behave normally.

Did this work before? Yes Started noticing this about a month ago.

Chrome version: 67.0.3396.87  Channel: stable
OS Version: OS X 10.12.6
Flash Version: 

Video: https://streamable.com/vg4zz
 
Screen Shot 2018-06-18 at 2.45.27 PM.png
117 KB View Download
Some things that are affected are: 

network tab is completely unusable as you can't scroll to see any requests
console tab fills up and becomes un-scrollable (as if overflow-x was set to hidden/none in css-speak...)
elements tab is unreliable and the live-preview is highly unstable
the orientation and placement of the devtools components are crazy and unpredictable...
Labels: Needs-Triage-M67
Labels: TE-NeedsTriageFromHYD Triaged-ET OS-Android
The issue seems to be related to OS-android. Hence, adding appropriate OS label and forwarding the issue to inhouse team for further triaging.

Thanks...!!
@krajshree@chromium.org, sure no problem. Let me know if you can reproduce it or not. I can provide more details, just want this fixed. :)
Labels: -TE-NeedsTriageFromHYD Needs-triage-Mobile
Cc: pnangunoori@chromium.org
Labels: Triaged-Mobile Needs-Feedback
dev@ -- Thanks for reporting this issue. Tested by connecting to Pixel XL Android 8.1.0 device to Chrome #67.0.3396.87 on Mac 10.13.3 and was not able to reproduce the issue. Was able to access the network tab, no errors were seen in console.

Could you please confirm whether it is observed only when emulators are connected or also reproduced when any physical device is connected. If so, please share the device details as well (Is it for the devices whose OS is less than 7.0).

Thanks!
The bug happens with android API 23, so a much older version than your test
device. I'd recommend using android studio to test this reliably.

I don't believe an emulator is required but you also can't just plug in any
phone you have in the room, it seems to be specific to an older version of
Android.
Project Member

Comment 8 by sheriffbot@chromium.org, Jun 21 2018

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
What's the Chrome version on your Android device?
It's an emulated android device from the latest version of Android studio.
I have no idea what version that ships with, probably the latest, but it
should be the same for everyone running android studio.
Cc: jbanavatu@chromium.org
Labels: TE-NeedsTriageHelp
Tested the issue  using #67.0.3396.87 by connecting Sony C6902 Android 4.4.4 with build 14.4.A.0.108 to Mac 10.13.3 as per steps mentioned in comment#0. Was able to access the network tab, no errors were seen in console.

As per comment # 10 it may require emulator or Android Studio ,adding TE-NeedsTriageHelp label  for more inputs from dev team on this issue.

Thanks!
Cc: kayce@chromium.org
Owner: einbinder@chromium.org
Status: Assigned (was: Unconfirmed)

Sign in to add a comment