SDK 3.1 - Versa Lite & i18n!

[JonFitbit]

Announcing SDK 3.1 which adds support for the new Fitbit Versa Lite, and the ability to localize your apps and clock faces with our new i18n API.

https://dev.fitbit.com/blog/2019-03-18-announcing-fitbit-os-sdk-3.1/

[EmTe]

According to the blog, apps were made automatically available for Versa Lite if compatible. How do we know if our apps were automatically converted or should we recompile ALL apps just in case?

---

Before Versa Lite was available to the general public, all apps and clock faces deemed to be compatible, were automatically made available without requiring them to be rebuilt with SDK 3.1 and the gemini build target.

---

[Gondwana]

Look in the GAM page for each app.

[EmTe]

---

@Gondwana wrote:

Look in the GAM page for each app.

---

I did but all my apps didn't have any indication that they support Versa Lite, enough for apps which I'm pretty sure don't use the barometer and physical buttons. So I'm wondering whether it was done without UI feedback.

[Gondwana]

I had a couple of my apps were white-listed automatically, and that's where it showed.

They look for reference to physical buttons, orientation, gyroscope, barometer and elevationGain (at least).

The Powers That Be acknowledge that the white-listing might have missed some Lite-friendly apps; you may need to re-upload and submit for review.

[EmTe]

---

@Gondwana wrote:

I had a couple of my apps were white-listed automatically, and that's where it showed.

---

I had some really basic app which didn't use any permissions and they weren't automatically converted. Actually I suspect it is because my apps were compiled with SDK 1.0 and they probably only convert apps compiled with SDK 3.0.

[Gondwana]

You could be right. I think they're now up to SDK 3.1 as well.

[jeremiahlee]

Great update with the i18n!

Proposed change: update buildTargets to use modelName instead of the weird alias names that don't mean anything to people outside of Fitbit.