Issue metadata
Sign in to add a comment
|
console.log(...) no longer logging to logcat
Reported by
da...@davidmanouchehri.com,
Dec 30
|
||||||||||||||||||||
Issue description
Steps to reproduce the problem:
1. Install Chrome 71.0.3578.83 or newer on an Android device.
2. Run `adb logcat chromium:V "*:S"` to watch for messages.
3. Open a page with "console.log('test')" or any console.* functions for debugging.
What is the expected behavior?
The console.log message should have been mirrored to logcat. Example:
chromium [INFO:CONSOLE(3)] "test", source http://127.0.0.1/ (3)
What went wrong?
No messages were sent to logcat.
Did this work before? Yes 70.0.3538.110
Chrome version: 71.0.3578.83 Channel: stable
OS Version:
Flash Version:
I've searched for awhile and cannot find any official announcement on this change. #905251 seems to imply that such a change might be coming, but provides no commit references and the ticket isn't even closed yet.
,
Dec 31
,
Jan 2
cc'ing hazems@ and torne@ from issue 905251 for further inputs on this issue. Thanks!
,
Jan 2
Are you talking about log messages from pages loaded in Chrome, or in a WebView? The WebView team are intending to remove this in future (as issue 905251 says) but we haven't done so yet. It's possible that someone has changed it for Chrome already though?
,
Jan 2
I only tested Chrome, not WebView.
,
Jan 15
,
Jan 15
Working correctly on Chrome 71.0.3578.99 > adb logcat chromium:V "*:S" 01-15 16:26:28.914 8922 8922 I chromium: [INFO:CONSOLE(20)] "foo", source: http://output.jsbin.com/yupiral (20)
,
Jan 15
Are you using a release/production device and APK (i.e. not debug)? |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by da...@davidmanouchehri.com
, Dec 30