Build environment: macOS (but doesnt matter)
Moddable SDK version: Pebble fork based on 8.2.3 (git describe:
8.2.3-4-g25f1a3bb1), as vendored in PebbleOS third_party/moddable/moddable
Target device: Pebble watch (ARMv8-M, MPU-enforced privilege separation).
Reproduces both on real hardware and on the Pebble QEMU emulator
Description
According to some reports, after the update adding xsbug support to Pebble, console.log calls no longer output to the Pebble APP_LOG, even when building in Release/non-Debug builds
Steps to Reproduce
- Build and install an app that has console.log using
pebble build and pebble install --logs (note that this isnt a debug build that will start xsbug)
- See (no) logs
Expected behavior
Logs will still write to Pebble's APP_LOG, especially when not built using --debug
Other information
We've had a few reports of this:
https://www.reddit.com/r/pebble/comments/1ui04hk/i_am_going_insane_re_cloudpebble_javascript_sdk/

Build environment: macOS (but doesnt matter)
Moddable SDK version: Pebble fork based on
8.2.3(git describe:8.2.3-4-g25f1a3bb1), as vendored in PebbleOSthird_party/moddable/moddableTarget device: Pebble watch (ARMv8-M, MPU-enforced privilege separation).
Reproduces both on real hardware and on the Pebble QEMU emulator
Description
According to some reports, after the update adding xsbug support to Pebble, console.log calls no longer output to the Pebble APP_LOG, even when building in Release/non-Debug builds
Steps to Reproduce
pebble buildandpebble install --logs(note that this isnt a debug build that will start xsbug)Expected behavior
Logs will still write to Pebble's APP_LOG, especially when not built using
--debugOther information

We've had a few reports of this:
https://www.reddit.com/r/pebble/comments/1ui04hk/i_am_going_insane_re_cloudpebble_javascript_sdk/