Latest app version not correct?

[jrmclaugh]

The latest app version in the Google Play store is 3.39.2.  This page indicates there have been several releases since then.

Why are these not available in the Play store?  I've been having plenty of random issues and want to be sure I'm using the latest app.

[Odyssey13]

Hi @jrmclaugh  my older phone and tablet can't get the newest Fitbit app, but my newer phone can. Your device can only install the version of the app that is for your phone's operating system. There isn't anything you can do to get the latest version if your phone doesn't support it.

[jrmclaugh]

Thanks @Odyssey13 

If that's what's happening here, that's pretty disappointing.  My phone isn't that old, Samsung Galaxy S8.

I don't see anything on that page indicating required android or phone versions, though.  I guess 3.39.x is an older series of releases, and 3.40.x is newer?  This forum also has a sticky saying 3.39.2 is the latest, which further confuses the issue.

[Kamamura]

The statement about "newest Android needed" seems dubious to me. The release notes clearly state that the minimum required version for download is Android 7, which was exactly the version Samsung Galaxy S8 was released with, but IMO since then it was upgraded to at least 9. I have checked all the Android devices available to me (3 phones and 1 tablet, Android 10 and 11), and all report that the version at Google Play store is 3.39.2. So version 3.40.x either does not exist, or was rolled back. Please provide only VERIFIED information. Thank you. 

[Odyssey13]

@jrmclaugh  my phone is the Samsung S8, running Android 9 and my app version is 3.40.1

[jrmclaugh]

Thanks for the clarification for your (same) phone, although that further confuses it for me.  Obviously something else is influencing this.

[Odyssey13]

@jrmclaugh I've asked a moderator to stop by to help us. Since it's the same phone, it does make me wonder, too. I automatically download the updates and it doesn't tell me when I got it, but the app says March 2nd when I ask for details. Could be when that version was released.

[SilviaFitbit · Accepted solution]

@Odyssey13 Thank you for your assistance on the thread and for flagging this post. 

@jrmclaugh, @Kamamura Hi there. Thanks for the details mentioned. Just wanted to clarify that a compatible operating system for Fitbit apps can be Android OS 7.0 or higher. 

In regards to the latest Fitbit app Android version, it's 3.41; however, the release it's a phased rollout which means that not everyone will get it at the same time. This post will be updated, once it's released to everyone. 

Hope this helps. Have a nice day. 

[CoachGail]

Is your sync working?  Mine is not and I was told I need 3.41

[MissBlade79]

3.41 broke my app. So don't be in a hurry for it. 

[t.parker]

3.41 is broken. Bad news is that 3.41.1 (beta) is broken, too. Seems like whole QA team walked out the door 😋

[t.parker]

@SilviaFitbit this is what's broken:

Not sure what's enrollment activity (I believe it may be related to Premium which I don't have) but I expect, if there are users who don't experience the crash, then those are probably Premium users. Following the crash log further, it looks like it tries to instantiate a non-existent class (which will fail with the ClassNotFound exception) which probably is a result of the error above (seems like a parsing error?). Time for your team to learn how the debugger works, fix the app, and maybe (I believe it's optional in Fitbit) test it before releasing it.