Developer Preview - Fitbit OS 1.1 BETA4
chevron down
back search icon cancel search

Fitbit OS 1.1 BETA4 - Developer Preview

Release Notes - Nov 22nd 2017

We're excited to announce a new firmware update! BETA4 (27.30.5.16) provides greater stability and performance, whilst also resolving a large number of issues.

Fixes/Improvements

  • Loading screen added

  • Optimized memory layout to make JS apps launch faster

  • Clock face developers can get stuck in a boot loop

  • Receiving empty file caused JS app to crash

  • Clock API doesn't tick on wake

  • Importing geolocation API powers up GPS immediately, now fixed

  • GPS JS APIs getting only position unavailable and ignoring timeout

  • gradientRect reboots device

  • JS apps should not crash on close

  • Tick event on display wake when granularity is set to off

  • Icons of side-loaded apps don't get removed when app is deleted until reboot

  • last-synced timestamp reports in future

  • A try-catch block logs errors even though the catch is executed

  • The value attribute is missing from TileList widgets

  • App fails to launch if manifest is slightly larger than expected

  • App install/launch error even though everything works

  • We now fail to install JS apps over 10mb in size

  • Goals API reports incorrect units for threshold values

  • TileList widget incorrectly checking virtual status

  • Clock error shown when installing a clock over WiFi

  • JS Memory app causes Ionic to crash

  • Added a lock to prevent system apps disappear/corruption

  • "Unhandled RangeError: Out of memory: Snapshot create failed..." printed on syntax error

  • Any parser error is cryptically reported to the developer as a out of memory error

  • Developer Bridge connection unusable on flaky WiFi - triggers reconnect on websocket

  • Some developer connections fail unnecessarily

  • Send the exception log as a single message

  • Allow Fitbit Studio to display uncaught exceptions correctly

  • Element constructor not on document, causes app crashes

  • App crashes when using getElementById on some elements

  • mask elements don't refresh when changed

Known Issues

  • Watch may crash if developer connection fails

  • Watch can crash when closing misbehaving apps

  • Firmware update fails after factory reset, if a JavaScript clock is selected