connect iq SDK v4.1.0.beta1 vs v4.0.10

Sorry, maybe I missed this.

Can someone explain me the version numbers of the connect IQ SDK please.

v4.1.0.beta1 is from 2021-10-12, but it includes the functions to access BodyBattery and StressLevel.
v.4.0.10 is newer from 2022-02-09, but these functions are missing. And according to the version number it's older than 4.1.0?

I'm really confused? Which is the latest SDK? And which should I use to develop Apps for a Fenix 7s?

Thanks for enlighten me

0 nonparametric over 3 years ago in reply to jim_m_58

Thanks for the tip, I just tried playing around with has.

And I also discovered (maybe you knew this already): I just tested and was able to display VO2Max on a Venu 2 watchface (real device). So it looks like the "beta" features in SDK 4.1.0 are now live on at least that device!

0 jim_m_58 over 3 years ago in reply to nonparametric

Look at the API level on the venu2, and with the latest FW, it's got a CIQ Api level of 4.1.1. 4.1.x and 3.3.x ("System 5") will be rolling out to other devices.

0 Cristi B over 3 years ago

4.1.1 is available. Does anyone know when software will be updated on watches? For example body battery is not available, and simulators don't have it either, so it's there but we can't even test it.

0 Felipe over 3 years ago in reply to Cristi B

Venu 2s (and I assume other Venu 2 as well) works both in the simulator and real watch. I believe that the API documentation about body battery and stress has changed since the beta, so have a look as they might have changed it.

0 flocsy🤠 over 3 years ago in reply to Cristi B

There are many watches that already got the upgrade: forums.garmin.com/.../connect-iq-system-5-sdk-now-available

0 Cristi B over 3 years ago in reply to flocsy🤠

Thanks, if i chose one of the supported watch simulators it works. I was expecting to see a setting on all simulators but can't find on any.

0 jim_m_58 over 3 years ago in reply to Cristi B

One thing to keep in mind is WW vs APAC versions of the devices.

The list of devices with System 5 APIs is for WW (World-wide) devices and may not include APAC (Asian-Pacific) variants.

So if you publish something with the new calls, it could crash on APAC devices. (APAC FW can be months behind WW FW)

You may consider setting the min API level to be 3.3.x, but that's not the whole solution. Consider this:

WW Venu has a 3.3.x VM (works)

APAC Venu has a 3.2.x VM (will not be available for this device since it doesn't meet the min API level)

WW Venu2 has a 4.1.x VM (works)

APAC Venu2 has a 4.0.x VM (meets the min API level, but will crash on device)

Jungles isn't the solution, as there, you can't differ things based on WW vs APAC versions.

What you want to do is use "has" to check if the System 5 API is available on the device at runtime. With that, you can handle the APAC Venu2 (the above example) without crashing. That way your app can adjust when something like body battery isn't available on an APAC version yet