Is there a way to see the console.log from the watch?

[JakeScott]

I have a watch face that works well in the simulator and works somewhat on the device. Do the console.log outputs continue to happen when the app is running on the device? I'm thinking there may be clues in the log output as to why it's not quite working on the watch. Is there a way to see them - maybe from the companion app? I know the only way to get data from the companion to the watch is with messaging, but can it work the other way as well? Request data from the watch from the companion? If the console.log isn't available on the watch, I suppose I could write log entries to a file on the watch and return that in response to a message request from the companion, if that's an option.

[Gondwana]

console.log works the same on physical hardware as on the sim.

Messaging is not the only way to communicate. File transfer is more reliable. Either approach can push data in either direction.

[adiroiban · Accepted solution]

It will work on the device, as long as the device is connected to the Developer bridge.

You can see them in the Studio web app or in the CLI tool. I prefer CLI.

But I can't find a way to see them while the watch is not connected to the dev bridge.

[Gondwana]

You can also see and copy log output from within the Fitbit app for sideloaded apps: in mine, it's 'Logs' at the bottom of the screen for the app.

[JakeScott]

Perfect! I never noticed that before. Thanks.