Issue metadata
Sign in to add a comment
|
Mobile remote debugging window is blank
Reported by
js...@acemetrix.com,
Jan 17 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3322.3 Safari/537.36 Steps to reproduce the problem: On Mobile device: 1. Connect Android device to desktop with USB Debugging enabled 2. Open Chrome or Chrome beta and navigate to any webpage On Desktop device: 1. Open Chrome Canary > DevTools > Remote Devices 2. Find the Android device, connect to it, and click "Inspect" on the webpage What is the expected behavior? On the desktop device, clicking "Inspect" should bring a popup window with Mobile Debugger (dev tools + screen mirror emulation) What went wrong? Instead, the Inspect window is completely blank Did this work before? Yes personally last observed working in Late November 2017 / Early December 2017 Chrome version: 65.0.3322.3 Channel: dev OS Version: OS X 10.13.2 Flash Version: Issue 801835 appears to be similar, however the author does not provide clear steps to reproduce. Thus, I was compelled to submit this issue specifying Mobile remote debugging. This Stackoverflow post describes the same issue: https://stackoverflow.com/q/48160837/1799146
,
Jan 17 2018
Could you please copy the version of your mobile Chrome browser here (it can be found on the 'Remote Devices' pane)?
,
Jan 17 2018
On my Samsung Galaxy S7 edge (USA-unlocked), I'm running these browsers--both of which have this issue: Chrome Beta (64.0.3282.85) Chrome (63.0.3239.111)
,
Jan 19 2018
I would like to add that I re-tested this issue in the normal Chrome browser, Version 63.0.3239.132 (Official Build) (64-bit), on the same Mac OS X 10.13.2 High Sierra laptop. The Remote Device debugger/inspector worked fine in Chrome 63.x, so this issue is a regression in Chrome Canary 65.x. Testing was performed using the same Android device as before with Chrome Beta (64.0.3282.85).
,
Jan 22 2018
,
Jan 22 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/bfc020eb4e62925b0cef14fe8e7cc40dd5a8b774 commit bfc020eb4e62925b0cef14fe8e7cc40dd5a8b774 Author: Dmitry Gozman <dgozman@chromium.org> Date: Mon Jan 22 21:26:36 2018 [DevTools] Fix InspectorFrontendHost.isUnderTest not present in newer Chrome We should return false for backward-compatibility with older frontends. Regressed here: https://chromium.googlesource.com/chromium/src/+/baf650e823bb8fd2615e6ec2920b46600d2a7585. Bug: 802928 , 801835 Change-Id: Ibbe3a932467f5c4cb7c6db49bef12f5c10a40926 Reviewed-on: https://chromium-review.googlesource.com/879166 Commit-Queue: Andrey Lushnikov <lushnikov@chromium.org> Reviewed-by: Andrey Lushnikov <lushnikov@chromium.org> Cr-Commit-Position: refs/heads/master@{#530999} [modify] https://crrev.com/bfc020eb4e62925b0cef14fe8e7cc40dd5a8b774/third_party/WebKit/Source/devtools/front_end/devtools_compatibility.js
,
Jan 23 2018
Tested this issue on Mac OS 10.12.6 by connecting to a Android mobile on the latest Chrome Build 66.0.3329.0 by following the steps mentioned in the original comment. Can observe Mobile Debugger on clicking on Inspect on the Desktop. Attached is the screen shot for reference. Hence adding TE verified labels as the fix is working as intended. Thanks..
,
Jan 23 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/9dcedc4b74321032789ab596f57d55999bacdfe3 commit 9dcedc4b74321032789ab596f57d55999bacdfe3 Author: Dmitry Gozman <dgozman@chromium.org> Date: Tue Jan 23 19:03:08 2018 [DevTools] Fix InspectorFrontendHost.isUnderTest not present in newer Chrome We should return false for backward-compatibility with older frontends. Regressed here: https://chromium.googlesource.com/chromium/src/+/baf650e823bb8fd2615e6ec2920b46600d2a7585. TBR=dgozman@chromium.org (cherry picked from commit bfc020eb4e62925b0cef14fe8e7cc40dd5a8b774) Bug: 802928 , 801835 Change-Id: Ibbe3a932467f5c4cb7c6db49bef12f5c10a40926 Reviewed-on: https://chromium-review.googlesource.com/879166 Commit-Queue: Andrey Lushnikov <lushnikov@chromium.org> Reviewed-by: Andrey Lushnikov <lushnikov@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#530999} Reviewed-on: https://chromium-review.googlesource.com/881811 Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/branch-heads/3325@{#33} Cr-Branched-From: bc084a8b5afa3744a74927344e304c02ae54189f-refs/heads/master@{#530369} [modify] https://crrev.com/9dcedc4b74321032789ab596f57d55999bacdfe3/third_party/WebKit/Source/devtools/front_end/devtools_compatibility.js
,
Jan 25 2018
Verified the fix on Mac 10.13.1 Chrome version #65.0.3325.18 as per the comment# 8 Attaching screen shot for reference. Observed Mobile Debugger when clicking on Inspect on the Desktop Hence, the fix is working as expected. Adding the verified labels. Thanks...!!
,
Jan 25 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by kozy@chromium.org
, Jan 17 2018Status: Assigned (was: Unconfirmed)