SDK 4.0 status

[JonFitbit]

We wanted to give a brief update about the status of SDK 4. To ensure a smooth rollout, we’re waiting until Fitbit OS 4 has been fully released to all in-market smartwatches before releasing the updated SDK. We have taken this approach to ensure that all devices are ready for any clocks and apps built with SDK 4. We can’t wait to get this release into your hands, and see all of your exciting new creations.

[FitnessJunky]

Do you have any timeline or date?

[paperinik]

Hey Jon, I've seen a bunch of people complaining about Fitbit OS 4.0 bricking their Ionic. The release notes say only "bug fixing" so I removed the Ionic from my account until we know better. But is it possible to get at least a list of new features in the OS? Thanks!

[Rajid]

How about some detailed API 4.0 documentation, showing the added/changed routines?

[JonFitbit]

@FitnessJunky no date announced yet, just Soon:trade_mark:

@paperinik I wasn't able to find out anything about bricked Ionics, only that you should ensure the Fitbit mobile app is up to date.

@Rajid Docs will come with the SDK release.

[paperinik]

@JonFitbit example post: https://community.fitbit.com/t5/Ionic/Fitbit-OS-4-0-1-Firmware-Release-27-68-9-12/m-p/3763880/highli...

[zhntr]

Not real useful - here's the "release notes" for 4.0.1:

This release includes bug fixes and improvements.

[paperinik]

@JonFitbit if I haven't upgraded to 4.0, will I be upgraded to 4.0.1 directly when I decide so?

[gaperton]

Interesting. So, that’s why my Ionic was bricked few days ago. I’m remembering being intrigued what could possibly break in a hardware which is extremely reliable by design. Well, now it’s at least makes sense :).

@JonFitbit, if there would be discount pricing for developers, I wouldn’t mind getting me a new device. 😉 

[rottenshark]

Isn't it much more useful to your ecosystem to release the SDK to developers as soon as possible, so that when you have SDK 4 rolled out, there are already apps to make use of it? Just make sure they can't be uploaded to the store and all should be good. Or even better, allow them to be uploaded to the store to get some beta testing going of the new features and let users know what they can look forward to once they get the update.

And honestly, even just getting a list of features would be great, just so that we could start thinking about ways we could improve our apps using those features.

[FitnessJunky]

@rottenshark 

Agree 100%.    

[Streeter80]

Is there any new updates or timeline info for when this will be released. I was so excited for the release of the Versa 2 I preordered and bought one for my friend, mom, and myself. I am now regretting it.

[gaperton]

It is sorta released. You need to use CLI tools. Edit package.json to make sure that these lines look like shown below (@fitbit/sdk version and "mira" in buildTargets), and do `npm install` once. Then you good to go with your Versa 2.

  "devDependencies": {
    "@fitbit/sdk": "^4.0.0",
    "@fitbit/sdk-cli": "^1.7.0",
...
    "buildTargets": [
      "mira",
..
    ],

Fitbit Studio doesn't work though (last time I checked).