11-09-2018 13:08 - edited 11-14-2018 00:29
11-09-2018 13:08 - edited 11-14-2018 00:29
As you may have noticed, the rollout of Fitbit OS 2.2 has been taking longer than expected. This is primarily due to a firmware upgrade issue that is affecting some users who received the update. We have been contacting those affected users to provide instructions and ensure they have a smooth transition updating to the new firmware.
Until this rollout is complete, you may wish to target SDK 1.0 to ensure your application updates continue to be available to all users. If your application specifically requires functionality in SDK 2.0, or you wish to update your device now, then you can perform a factory reset and your device will be upgraded to Fitbit OS 2.2. Please note that factory resetting your device clears all data including music, Fitbit Pay information, and apps, however all of your Fitbit data is still available in the Fitbit app.
11-09-2018 13:22
11-09-2018 13:22
I just performed a factory reset and received 2.2. Looking forward to testing applications on it directly. Can you provide any feed back related to having less memory available compared to v1 SDK?
11-10-2018 08:07
11-10-2018 08:07
@wiseman13 wrote:
I just performed a factory reset and received 2.2. Looking forward to testing applications on it directly. Can you provide any feed back related to having less memory available compared to v1 SDK?
Thanks, I've passed this onto the firmware team.
11-14-2018 11:43
11-14-2018 11:43
Is there an ETA on when the firmware issues are resolved and we should start targeting framework 2.0 again?
11-14-2018 11:51
11-14-2018 11:51
@jomis003 wrote:
Is there an ETA on when the firmware issues are resolved and we should start targeting framework 2.0 again?
We'll notify when it's a good time, no fixed ETA yet.
11-30-2018 05:07
11-30-2018 05:07
@JonFitbiti think i am one of the affected users of the 2.2 update. Its stuck in eternal boot loop after trying to get 2.2 update. now the ionic is unusable.
12-09-2018 17:14
12-09-2018 17:14
Any more update on when the version 2.0 will be rolled out to devices?
12-16-2018 06:24
12-16-2018 06:24
Bump.
Over a month and still not fixed.
12-18-2018 13:59
12-18-2018 13:59
Ha. Never mind. 3.0 It is...