Announcing Fitbit OS SDK 4.1

[JonFitbit]

SDK 4.1 adds a new API for calendar access, Always-on Display API, detecting a user's primary goal, and some rather useful enhancements to the Document API.

https://dev.fitbit.com/blog/2019-12-19-announcing-fitbit-os-sdk-4.1/

[Jemand]

As soon as I add the permission "access_aod" I can install the app on the simulator but not on my Versa 2: "Error installing app" When I remove the new aod-permission it works again. Is there any trick to install my watchface on my watch with this new access_aod permission?

[Gondwana]

At this stage, Fitbit doesn't allow unapproved clockfaces/apps that use access_aod to run on physical devices until the app/clockface has been manually assessed to be non-damaging to the device.

[curxxx]

No, Jemand, you may not make AoD apps. Did you not read the post at all?

Additionally, Fitbit, this message is for you: Instead of focusing on new additions, how about you ensure what you already have works? Your entire development process is a buggy mess.

[JonFitbit]

@curxxx any specific issues you're referring to?

[j0nson]

Since you asked, @JonFitbit, setting custom exercise names has never worked, and there doesn't seem to be a resolution in sight, even though clearly stated as possible in the documentation:

https://community.fitbit.com/t5/SDK-Development/Custom-exercise-name-and-GPS-data/m-p/3881462

[soutarm]

I've had quite a few users request AoD and coming off developing watchfaces for Samsung smart devices I figured this would be a cinch. How foolish of me! After hacking the package.json and finally setting up something decent, I can't even test it on my actual Versa. Didn't I agree to something somewhere that says if I brick the watch it's my fault, you know, like almost every other developer license? This is beyond a joke and looking at the original date of this post it's been a long-running joke.