Fitbit app v3.11 for Android | Bugs - fixes

[LostEchoes]

Hi all.
As I occasionally like to live dangerously, I'm downloading the new version of the Fitbit app and will report back if I I find anything interesting.

Android Version 3.11 
Android Version 3.10.1
Android Version 3.10
Android Version 3.9.1 ~ Detailed reporting about fixes and bugs here.

Android Version 3.9 ~ Detailed reporting about fixes and bugs here.

Android Version 3.8 ~ Detailed reporting about fixes and bugs here.
Android Version 3.7 ~ Detailed reporting about fixes and bugs here.

Samsung Galaxy S7
Android OS 8.0.0

[malkith]

aye 3.9.1 app still fails to launch for me, sits at the white fitbit loading for a few then returns to the phones desktop

[SunsetRunner]

@malkith what phone are you using and what version of Android are you running?

Just trying to figure out if I  should install the app or not.

Version 3.8 is a little buggy but at least it works.

Samsung Galaxy S7 Android version 8.0.  Security update done last week on phone.

[malkith]

moto z2 play  android 8.0  8/27 security update

i got a new versa 2 last thursday after giving up on my versa (wouldnt sync but the app would launch)
versa 2 synced like a charm no idea if this was before or during the rollback to 3.8 last week

everything was fine for 24ish hours then started getting fitbit has stopped working popups, clear cache, force stop, multiple reinstalls, app just wont get past the white loading screen with the fitbit logo

[SunsetRunner]

@malkith ugh doesn't sound like I want to update to this version if the normal workarounds don't work 

@LostEchoes are you still experiencing crashes with the 3.9.1 version of the app? 

[malkith]

@SunsetRunner  yeah  i try launching it every day or other day just to see if it "fixed" itself

[LostEchoes]

@SunsetRunner 
After the 2nd crash, I returned to 2.90. I just can't bother to be a permanent ...beta tester any more for a company that doesn't seem to care. 2.90 is much more stable, it does not crash and it syncs without issues (like 99% of the times). 
As I have previously stated, I'm willing to test every new 3.x version that's coming out, just to see if they have fixed any of all these bugs, but I do not intend to stay with the buggy versions for more than 1-2 days.
My advice: stay with 3.8 for now.

[malkith]

3.8 was what the appstore installed after they did the roll back last week
i tried 3.7 but that did the same

maybe ill try 2.9

[SunsetRunner]

@LostEchoes it's a shame that Fitbit keeps putting out app versions that continue to have bugs.  Every 3.x has had issues that haven't been fixed and additional issues pop up.

I'll stay with 3.8 at least it works but will download another version that I know works 3.7 or 2.90 if this one acts up.

[LostEchoes]

It seems that version 3.9.1 has also been pulled out of the play store and 3.8 is now again the latest version available.

[malkith]

Yeah 2.9 wasn't the solution

But it crashed faster. Under a second 

[LostEchoes]

I did have one crash (for the first time ever - and the last) with 2.90 right after I uninstalled 3.9.1 (the 2.90 crash seems to have been caused by the leftovers of 3.9.1), but then I tried this:  I deleted Cache and Data, uninstalled 2.90 and restarted my phone, I re-installed it and I have not had any crash with 2.90 again since then.
So, for me, even temporarily 2.90 IS the solution. By far a version with stability & fewer bugs. 

[SunsetRunner]

@LostEchoes I just checked Play Store and 3.9.1 is no longer available for me either just a showing the current version that I'm on 3.8 as available. 

[LostEchoes]

Yesterday I saw that (a) 3.9.1 version has been out on Play Store again.
So I posted my thoughts at this thread:

https://community.fitbit.com/t5/Versa-Smartwatches/Distance-on-GPS-map-doesn-t-match-with-exercise-s...

1) asking how come a 3.9.1 (and not a 3.9.2) version has been released again with the same version number as the previous one, and whether it is the exact same version as the old 3.9.1 that was pulled. I wanted to know if this 3.9.1 has any differences and fixes. 

2) quoting this very helpful post by a Fitbit moderator where she explains how the distance is calculated, a post that could help us understand what's going on with the "Connected GPS inaccurate Distance" issue that has been reported by some many people.

Moderator edit: word choice

[SunsetRunner]

I'm glad I don't have my app to be updated automatically.

You brought up a very valid point with the app....why rename it the same, is it the same version, have the bugs been fixed as far as crashing, syncing,  notifications that users have been experiencing since the start of the 3.x  versions?  I think as users we should be made aware that issues have been resolved.   It would eliminate so much frustration.  This just sends a very poor message that Fitbit doesn't care about its customer base. 

It's a shame that all Fitbit products are affected with various issues on both the Android and iPhone platforms and nothing is being done to address and correct these issues correctly.

Moderator edit: word choice

[LostEchoes]

I don't know what this could mean, but right now 3.9.1 is once again pulled out of the play store and 3.8 is again the latest version available.

 

 

[SunsetRunner]

@LostEchoes  3.9.1 was showing this morning as being available and I just checked as well and it's showing version 3.8 as the latest version on my end.

Maybe they realized again that 3.9.1 was still a version with a lot of bugs.

You can't expect users to do all the various troubleshooting and workarounds version after version when it just doesn't work.  Plus by now we all know what troubleshooting  steps to do before posting on here.  The app has bugs (all versions of 3.x have had one issue after another and each version gets worse) fix it so works once and for all. 

[LostEchoes]

Version 3.10 now seems to be the new / latest one on Play Store.

Updated: November 12, 2019
What's new:
*We made improvements to exercise details so that you can easily see what your average and maximum heart rate were during your workout.

[SunsetRunner]

@LostEchoes 

It's not available on my end yet. 

That's  it?  That's all that's new?

What about fixing the bugs and making the app stable?

Doesn't sound promising. 

[LostEchoes]

@SunsetRunner 
Yeah it's a bummer. I mean I do welcome such detailed logs about what's new (that old generic "Bug fixes & performance improvements", etc doesn't really say anything at all), but I was hoping that log would also include 1-2 things about the long confirmed issues we have been facing. No such luck.

I'm also not getting what this specific change ("so that you can easily see what your average and maximum heart rate were during your workout") means and how it's reflected on the app. Didn't we already have this in the past? Not sure what has been improved / changed. Any feedback from anyone would be welcome.

Oh and I can also see another (new?) bug, this time with the UI. Here's a screenshot. 
Some of the stats seem to overlap other stats (on the bottom, where it shows the speed, etc). Maybe a screen resolution - related bug.

[LostEchoes]

An early report on some of the confirmed bugs (a detailed report will follow when everything is tested) :

1) When I try to add friends to Challenges, they show up with a status of "No recent activity". All of them. This has not been fixed on 3.10

2) Elevation Gain in activities is reported and wrongly shows as zero (0). I have not tested this yet with a new activity on 3.10, but the past activities still show up with Gain = 0. 

3) Connected GPS inaccuracies (distance, pace, etc). "The connected GPS starts playing up badly with incorrect distances measured". I have not tested this yet with 3.10. Waiting for feedback from other users, too.

4) Fitbit App - "View All Posts" link does not display ALL posts by a user, but ONLY the last 5 of them. This has not been fixed on 3.10.

5) Version 3.9 seems to be unstable and crashes on some users. I have not tested 3.10 for enough time to see if this is fixed now.

6) UI bug with stats overlapping other stats on the "Recent" tab of an activity. This is a bug I've just discovered and is probably related to the screen resolution. Reported here.