语言

Menu
Sites
Language
How to see console.log() if a real device is run?

How to see console.log() if a real device is run? Gear S3, 2.3.2

Maybe there are something else instead?

Thanks.

编辑者为: Anonymous 开 03 5月, 2019
列表

响应

11 回复
Marco Buettner

The some procedure like on emulator you need to connect your device to the pc and can check it via Log-Tab in the SDK.

To filter for console-messages, use "ConsoleMessage" as Tag on the Log-Tab and dont forget to setup the Debug-Levels on the same tab. (you should use V,D,E)

Thank you a lot for your reply however messages aren't shown. I'd been using both the real device and an emulated device with the same project before I wrote this topic.

Marco Buettner

Did activate the Debug-Mode on your Gear S3? 

Settings -> Gear info -> Debugging

Of course I did otherwise it wouldn't work at all.

I still don't know how to put log messages... Nothing work:

console.log console.log("console.log");
console.info console.info("console.info");
console.warn console.warn("console.warn");
console.error console.error("console.error");
console.debug console.debug("console.debug");

Who knows?

J. Schwartz

I'm also interested in an solution. When running a application in Debug Mode on emulator it works but not on physical devices.

Using .innerHTML on objects instead of console is really annoying...

Kiwook Hong

If you can use "Debug as" then web inspector will be launched. In the console tab, you can fine the console log.

Stefan Stoica

I have the same problem. On emulator, the console.log (error, debug etc.) output works but not on real device (Gear S3).

It's very annoying. Did anyone find out how to fix this?

André Reus

To debug Tizen web application,Google Chrome is mandatory .... console.log() will write logs on Chrome console if you select 'Run as Debug' mode your project ... 

Stefan Stoica

Thank you Andre for your answer.

Meanwhile, I've made some progress on this. I found out that the logs don't appear when I use them in a watch face. The debugger (Chrome) doesn't connect because the watch face is not launched after the deploy on a real device. Not sure if it's possible to attach the debugger when the watch face starts but as a workaround I removed the ".../category/wearable_clock" (only for debugging purposes) from category and the watch face is launched as an app and the debugger connects and works fine.