Announcing SDK 5.0 for Fitbit Versa 3 and Fitbit Sense

[JonFitbit]

SDK 5.0 has been released! Check out the developer blog post for all of the details!

https://dev.fitbit.com/blog/2020-09-24-announcing-fitbit-os-sdk-5.0/

[JonFitbit]

---

@SuperStevo86 wrote:

@JonFitbit When are these errors going to be fixed and does that mean any SDK 5.0 build that gets submitted for review in GAM will automatically be rejected because there are "errors" even though these errors can't be fixed by the developers as they are referencing "Fitbit" resources not accessible by developers?

---

No, the review team won't reject for these messages.

[Harboe]

You better not be to negative on Fitbit for leaving their users behind or they might remove your post, as they did with mine. What "great" customer service.

[gabriel-sasu]

i ve got the same issues, but these were not resolved when I changed the index and widget extensions.

Can you help me please?

[AyushJohri]

Hi Blyth, 

While when I am designing my clock face for Versa1, using the latest Fitbit Studio, I am getting the below error, can you help what does this mean

"Sideload of app failed. App was built for Fitbit Versa 3 and Fitbit Sense, but connected device only supports Fitbit Versa applications"

[Gondwana]

You've built your clockface using SDK5 and targeting the new watches. You need to select SDK4.2 and target Versa ('meson').

[SteezyFit]

I just bought this during 2019 winter break. Very sad to see this.

[GeekBit]

Where can I find the documentation for SDK v4.2 now? It seems that https://dev.fitbit.com/build/guides/user-interface/svg-components/ now only has the documention for v5.0. I want to look up how to handle components and tile-items for the Ionic:

     <use href="#tile-list-item" class="tile-item">

      <use id="item15" href="#checkbox-tile" >

        <set href="header/text" attributeName="text-buffer" to="15" />

      </use>

    </use>

[Gondwana]

https://community.fitbit.com/t5/SDK-Development/Access-to-the-older-4-2-SDK-Guide/m-p/4500394#M13203

[GeekBit]

Ok, using https://web.archive.org/web/20191102091359/https://dev.fitbit.com/build/guides/user-interface/svg-co... let me access the v4.2 documentation. But why can't Fitbit provide it?

Does Fitbit want us developers only to develop in SDK v5.0 for Sense and Versa 3 and forget about the other models like Ionic? 

I really would like to get a statement from Fitbit what their opinion is about SDK v4.2 versus SDK v5.0!

[Nevyn2]

JonFitbit wrote:

"SDK 4.2 was just released for those devices."

SDK 4.2 doesn't have much changes. The Always-On-Display is still not available for every developer. I guess it will never be...

[DeNitE_Appz]

How do we do this? Just upload the v5 as a new update? It won't over ride the previous 4.2 version?

[Gondwana]

Yes. Watches will get the most recent version they can run.

[n0ano]

I've just discovered that support for scrollview, tiles and tumblers has been removed for watch faces for the new devices, Versa 3 and Sense.  Ignoring how upset I am about this decision the least that Fitbit could do is document this change.  The page announcing the new SDK 5, https://dev.fitbit.com/blog/2020-09-24-announcing-fitbit-os-sdk-5.0/ , makes no mention of this feature and I can guarantee that this is a breaking change for my watch face - which utilizes these UI elements just fine on an Ionic.

[Nevyn2]

Fitbit is not developer friendly...

[Charge4User]

can you modify the way steps are counted? Add something similar to what Garmin is doing.
As far as the "just walking around" differences, Garmin devices have an "at least 10 steps" count to avoid false steps from just arm movements or other things that might count. What happens is no steps are counted until you do at least 10 steps, and then you are given credit for the first 10. So if you do 5 steps and then stop, they won't be counted by Garmin, but will by other vendors.

[MichaelAdamski]

Thanks for info, very useful post!