help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Fitbit OS 2 Breaking Change

‎03-21-2018 17:19

‎03-21-2018 17:19

Unless I'm mistaken, there's a behaviour change in Fitbit OS 2.0 that can break previously-working faces and apps. Under OS 1.x, accessing a SVG attribute that wasn't explicitly declared in index.gui (eg, .x) would return the default value (eg, 0). However, in OS 2.0, such an access returns 'undefined'. Subsequent use of this value can result in an exception which halts further processing.

 

This happened to my clockface in the store, and could afflict other apps (if they're as badly coded as mine). Developers might want to look out for this.

Peter McLennan
Gondwana Software
Best Answer
0 REPLIES 0