console.log wierdness

[Tim]

I have noticed a couple of issues wrt console.log()  when testing via livesync on tablets. I'm doing development using the in-browser clinet and doing livesync to test on devices. I rely on the log file as viewed via the Telerik companion app to diagnose my app.

When I livesync to a iPad client, the companion app shows each console.log message on a separate line. Good stuff nice an readable. However on a Samsung Galaxy S2 and a Huawei M2 (Android devices) the console.log messages are just one continuous stream of text. Not very friendly to read. Could somebody insert a \n in there on the Android companion app please?

 

Also it seems that only some of my console.log() messages are making to it to the log within the companion app. I'm not exactly sure of what's going on, but it seems that code directly associated with a view is ok, but console.log messages in other modules I define which are accessed by the view code don't seem to reliably show up on the log. 

 

 

 

[Tsvetina]

Hello Tim,

Thank you for reporting these issues. They are indeed present in the companion app and are logged for fixing. They will be addressed in the next version of the companion app. We apologize for the inconvenience caused by these problems.
Additionally, I updated your Telerik points as a token of gratitude for reporting the issues.

Regards,
Tsvetina
Telerik