Console.log broken in Chrome DevTools

[petekanev]

This is a:

• Bug report
• Feature request

Is this a real problem/a really cool feature?

• I checked and verified that the Feature/Issue is not already logged on SO
• I checked and verified that the Feature/Issue is not already logged on Github issues

Context:

The content of the first console.log ever to execute, after the Chrome DevTools are connected, will replace all other console logs displayed in the Console Panel in Chrome DevTools. The bug appears in Chrome 62 and up.

Note: The problem does not seem present inside VSCode, likely because the VSCode console prints out the CLI output, as opposed to the Inspector Console.

Your environment (if applicable):

• CLI: 3.3.0
• Runtime version: 3.3.1 (irrelevant)
• Cross-platform modules: 3.3.0
• Plugin(s): irrelevant
• OS: irrelevant
• Node and npm: irrelevant
• Device/Emulator: Android SDK Emulator API 26
• Android API Level: 26

Type of error (if applicable):

• Build-time
• Run-time

Possible solution/implementation:

Implement the Log domain of Chrome DevTools and send messages through its proper https://chromedevtools.github.io/devtools-protocol/tot/Log/#event-entryAdded event.

Reproduction steps/repo (if applicable):

• Open a debug session in Chrome DevTools using tns debug android and following the on-screen instructions.
• console.log("1");
• console.log("2");
• Console logging anything after the "1" string will not display the true text, but instead show "1"