Chrome Dev Tools Device Emulator Debug window not displaying correctly.
Reported by
simonste...@gmail.com,
Dec 18 2017
|
|||||||
Issue description
Chrome Version : 63.0.3239.84
OS Version: Windows 7
URLs (if applicable) :
Other browsers tested: n/a
Add OK or FAIL after other browsers where you have tested this issue:
Safari:
Firefox:
IE/Edge:
Android emulator created with Android Studio 3.0.1 emulating 1080X1920 screen, API 23, Target: Android 6.0
What steps will reproduce the problem?
1. Start Android emulator with a Cordova generated .apk .. as attached
2. In Chrome go to chrome://inspect/#devices
3. inspect app in emulator
What is the expected result?
Properly formatted Developer Tools debug page.
What happens instead of that?
Page is all over the place and is completely unusable.
However if the same .apk is installed on a usb-connected Android phone then inpecting that works correctly as previously.
Please provide any additional information below. Attach a screenshot if
possible.
This started with release 63.0.3239.84 on Dec 14
I successfully rolled back to Version 62.0.3202.94 and it works properly.
Screenshot available here:
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/google-chrome-developer-tools/qWg3OAGUIOY
posted by Gilles Boutroux
Attachment is an extremely simple Cordova app of the "Hello World" type.
Request. This error renders Dev Tools unusable for debugging Android applications created by Cordova and probably other systems such as Phonegap. It is extremely necessary that this is fixed.
If you need additional information ask me or one of the other people who have reported the bug.
,
Dec 18 2017
We're experiencing this issue in our workplace, when trying to debug a web app running in a webview, in a xamarin android app. So far it's happening for at least four people. Some things I've determined: It's not platform specific: we see it happening with Chrome on Mac OSX, Windows 7, and Windows 10. It's not specific to our web app: I created a simple "hello world" app, and it happens when debugging it as well. I can also confirm the report that it happens when debugging the app while it's running in an emulator, but not a device attached via USB. We've seen it with two kinds of emulators: Genymotion and the android sdk 23 emulators. However, even when remote debugging a real device, it's very slow and the device heats up to an alarming point. Workaround is to only turn on remote debugging right before you're going to hit your breakpoint. Inconvenient, but it works. It's not necessarily happening for everyone who tries: I tried on my home computer Friday night PST (Dec 15, 2017), and remote debugging of the web app in an emulator worked fine. When I tried again Sunday afternoon PST (Dec 17, 2017) remote debugging was broken. Some patch that went through, perhaps?
,
Dec 18 2017
Adding OS and component labels per comments. #2: Can someone experiencing the issue post their variations from chrome://version? This will help determine whether this might be related to any ongoing field trials.
,
Dec 18 2017
Google Chrome 63.0.3239.108 (Official Build) (64-bit) (cohort: 63_win_108) Revision d2626860fae283daee484943e6820af18fc73fd9-refs/branch-heads/3239@{#676} OS Windows JavaScript V8 6.3.292.48 Flash 28.0.0.126 C:\Users\jbell\AppData\Local\Google\Chrome\User Data\PepperFlash\28.0.0.126\pepflashplayer.dll User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36 Command Line "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --no-startup-window /prefetch:5 --flag-switches-begin --flag-switches-end Executable Path C:\Program Files (x86)\Google\Chrome\Application\chrome.exe Profile Path C:\Users\jbell\AppData\Local\Google\Chrome\User Data\Default Variations c134752e-b8b72c88 3095aa95-3f4a17df 6c43306f-7853f67b c5f9b398-ca7d8d80 7c1bc906-f55a7974 47e5d3db-3d47f4f4 1210a805-ecd831c b1edbc38-cf4f6ead d43bf3e5-bd7cd813 ba3f87da-45bda656 776de70c-eadfd437 79616653-3f4a17df f9884634-ca7d8d80 9e201a2b-6e3ce1c 68812885-4d2fac87 684d1cdf-160692dc 5e3a236d-4113a79e f347910c-3d47f4f4 4b61504a-d25ea691 9773d3bd-f23d1dea 8e3b2dc5-93702590 9e5c75f1-b6633ebc f79cb77b-3d47f4f4 4ea303a6-ecbb250e d92562a9-ca7d8d80 447469ba-13d9f35f 7aa46da5-c946b150 25fc488a-4d2fac87 1bced4a3-ca7d8d80 b2f0086-93053e47 ef25c1eb-ca7d8d80 4bc337ce-612a79a3 494d8760-6843eff2 f47ae82a-86f22ee5 3ac60855-486e2a9c f296190c-bca011b3 4442aae2-a5822863 ed1d377-e1cc0f14 75f0f0a0-6bdfffe7 e2b18481-7158671e e7e71889-e1cc0f14 94e68624-803f8fc4 f141d4bc-ca7d8d80 e9ce63c1-3d47f4f4 da4aaa01-ca7d8d80 Compiler MSVC 2017 (PGO)
,
Dec 18 2017
I can further report that this issue happens with Chromium Version 65.0.3299.0 (Developer Build) (32-bit) in windows 10.
,
Dec 18 2017
This is due to Cordova's using Chromium that is too old. The front-end for that old version of Chromium used /deep/ selector which is no longer supported. As a result, layout is broken beyond recovery. The workaround is either 1) push Cordova towards using Chromium that is less than one year old 2) download Chromium M62 and use it to open chrome://inspect
,
Dec 18 2017
Using an older version of chromium works here! Thanks a bunch. If you're using windows, just grab this one: https://www.googleapis.com/download/storage/v1/b/chromium-browser-snapshots/o/Win_x64%2F499024%2Fchrome-win32.zip?generation=1504219063821312&alt=media |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by g.boutr...@gmail.com
, Dec 18 2017