Distance goal miles to km conversion error

[JennaS1966]

I have Android moto G4.  I upgraded Fitbit to play the new Fitbit bingo (love it!).

However I noticed a glitch that happened in past month.. and I can only put it down to the upgrade .

My daily distance goal is 5 miles.  I went to update my activity goals and see it was on my dash as 3.11 mike's.  Odd, so I changed it back to 5 miles. However I noticed that when I had reached 5.2 miles... I was still a long way from green .

From what I can see, Fitbir seems to assume that my 5 miles is 5k (and has lowered my miles), but it is still calculating it on miles and not km 

I took SS when the front showed not green miles, bur the weekly dash DID. Then the weekly dash changed to 3.2 miles (nor green). Very confusing. 

I uninstalled and reinstalled Fitbit app,

 

 

 

 

but no change. 

Is there a system glitch ? 

Moderator Edit: Clarified subject

[PeteH3]

Ridgehiker, I believe you hit the nail on the head here. It's clearly a code logic issue within the Android app. Upon setting the desired distance goal within the app (in miles), and then syncing, the web dashboard shows the corresponding number of kilometers, properly converted. The dashboard has no way of knowing that you intended miles. If your units are set to miles in the dashboard, you just see the converted-to-kilometers number of miles (which is not the desired distance goal in miles anymore, but the dashboard shows it as miles). Seems like an easy fix for the app developer. Just check the code!

[pakmanpony]

This didn't work the other day but yesterday I went to my computer and opened the app and changed the 8.1 that was showing up there to 5 and my phone app and Ionic both are corrected and I get a completed circle.

[mjwexe]

Distance goal has always been 5 miles in the online (Windows) dashboard. The issue is with the Android App which has defaulted to 3.11 miles and if set to 5 miles registers the miles as 8 which , as has been pointed out numerous time in this thread, is the equivalent in kilometres, despite the distance unit in the Android app being set to miles.

[RidgeHiker]

Hi pakmanpony - Can you check your phone app and see if the distance goal changed to 3.1 miles?  That is what I see when I go through the change from my PC.

This the "Before" from my PC.  Note the distance goal is showing as 9.66 miles.  (my target is 6 miles per day)

This is "Before" screenshot from my phone.  Note it is 6 miles.

Then I changed my Distance goal on the PC to 6 miles

And it reflected on my phone as 3.73 miles.

It is coming up on 3 months since JennaS1966 first started this thread.  We need to keep posting and voting to get this on FitBit's priority list.

[pakmanpony]

 The first time, several weeks ago I changed the number on my desk top program it changed my Ionic and phone app to 3.1 this time it did not. All locations kept my goal as 5.0 miles and my completion circle on the phone app and on the Ionic now completes at 5.0 miles! Can't explain why it worked this time. I did recieve a firmware update on the Ionic last week. Now version 27.70.8.0

[RidgeHiker]

I hope it stays fixed for you!  I did the most recent firmware upgrade as well (I should have mentioned that), but no improvement.

[RoseVee]

I'm having the same issue. I set the goal as 4 miles, but it won't complete, even if I go for 6 miles. Haven't gone 8 miles to check if it will complete.

[Piscesrn]

It is likely that you will have to do 6.4 or 6.5 miles to complete your circle as 4 miles is 6.457km. 3.1 miles = 5k and I have to do 5 miles to complete my circle. 

If your goal is 4 miles. To complete  your circle at 4 miles you will need to set your miles goal in your app at 2.45 or 2.5 miles 

[RicardoFitbit]

Hello again! It's a pleasure for me to continue providing assistance on this thread.

First of all, I'd like to appreciate all the information that was shared and your patience with this situation, I understand that this conversion error can be really frustrating for you guys. I'd like to share that we’re aware of this situation and currently working to resolve it as soon as we can. That said, please be sure to keep your Fitbit app up-to-date to ensure you receive the quickest resolution. Your patience is really appreciated while we look forward to getting you back on track with this issue resolved.

Please let me know if there's anything I can do to assist you in the meantime.

[brettpersson]

FitBit charger doesn't have a problem taking my monthly payment for their premium service but apparently can't fix the conversion problem.  After waiting way too long I am canceling my premium account.  I have one a Fitbit for the past eight years but I'm done.

[RidgeHiker]

Hi RicardoFitbit - Thank you for the update.  I appreciate how hard it is to keep a complicated application working for so many platforms and devices.  But, this is still happening, and his been going on for nearly 5 months.  Is there a target date or any timeframe for the fix?

[JennaS1966]

After I started this thread I had an exchange of messages with Fitbit on their Facebook messaging system. They concluded that my phone was now too old to function with the most recent updates to the firmware.   Two weeks ago I bought  Samsung S20.  Guess what.  No change.  Still the same issue where it erroneously converted the miles and kms .

Fitbit please let us know when you are going to fix this issue  

[Tdawgg777]

So this issue has been happening to me as well... I rolled back to app version 3.15 from Feb and the distance goal is working as it should... from app version 3.16 onward, including the latest release from Aug 4th the distance goals are wrong im sticking with 3.15 and disabling updates for the Fitbit app in the Playstore. And the suggestion from Fitbit that you need to upgrade your phone is definitely NOT helpful... as im using an old budget LG with android 8.1 on it and after reverting ro the older version it works fine... Fitbit, have your developers take a look at what the did wrong in version 3.16 and revert the changes... maybe double check that something else doesn't get "broken" while "fixing" this issue. Seriously, the amount of times I have had to revert the app and restrict updates is just unacceptable. Let not even mention the sync issues I've had since I first got the charge 3 and still have with the versa I now use.

[RidgeHiker]

Thanks Tdawgg777!  That release lines up with when JennaS1966 started this thread.

Also, with JennaS1966 letting us know it still broken, even on a new phone with a new OS, we know this is a coding error.

Come on Fitbit, this is bug...  Do the code compares back to version 3.15 and see what changed in the km to miles conversion. 

[PeteMJ]

1/2 a year out and they still have a conversion error.

How much could have changed from 3.15-3.16? If it was such a significant overhaul that analysis is difficult, why are the version numbers so close together?

I'm on a Galaxy S10,  a phone the developer explicitly lists in its compatibility list and is 1 year removed from being the manufacturers flagship model. This is ridiculous. Is it a relatively small gripe in the big scheme of things? Yes. Is it an embarrassing error that a billion dollar company should be able to address within 6 months of being told about it? Also yes.

[NSJ1991]

Still having this issue....last update from moderator was mid june...its September tomorrow and still no update/fix..what a joke...I raised this via email and was asked to send a screenshot showing WHEN it was set to KM instead of miles?! Sick of seeing my temperature in F instead of C too. Annoying! 

[Brrb66]

My Fitbit displays 8.4k and equates this to 3.4 miles (it should be 5.28 miles!) So it looks like the conversion km to miles is always wrong and my miles appear much lower than they should be 😞

[NSJ1991]

This is just ridiculous now....still having the same problem! Each time I 'fix' the units either on the dash or on my app it just changes automatically to represent kilometers instead of miles and my weather app is showing F instead of C.

I saw there was an update the other day and got excited that this had finally been looked in to (as promised in june!) But no....nothing...still the same stupid issues. Please can a moderator come back with an update?

The customer service team who I am in an email battle with are just not understanding at all...its been weeks and the issue has been escalated and I'm still being asked to check my units are correct in my app 🤦🏻‍:female_sign: 

[MaryE2]

Throwing in my two cents to keep this thread up to date.

My app updated to Version 3.32 on Oct. 13, 2020 on my S10, and this km-miles conversion issue started for me. Exceptionally frustrating to see that we're 7+ months into a known issue with an easy fix, but nothing is being done.

Support your users, Fitbit. 

[Grail1223]

I reported the issue last week to the support line.  After several suggestions of disconnecting my fitbit from the app, and re-installing the app itself, I received an email that they are aware of the issue and will fix it as soon as possible.  Based on this thread of 7 months or more, I don't expect anything soon.  It's very frustrating, especially when one can see from this thread exactly when the issue started so it should be easy to go back to the old version of code and determine where the mistake is.