What's wrong with the distance goal?

[MarioDings]

I found this on todays results:

as you can see my target is 5 miles, my distance is 5.32 miles but my target is not hit on the second screen. What is wrong Fitbit? 

Did some extra research. My dashboard in the browser says 4.85 Miles. So I reduced it (again) to 3 Miles. On my phone It says now 1.86 Miles. There's something wrong. I know there hes been another post on this, bu I can't find it anymore.

Found it!:

https://community.fitbit.com/t5/Android-App/Distance-goal-miles-to-km-conversion-error/m-p/4137459

Now I'm getting worried:

https://community.fitbit.com/t5/Android-App/Distance-not-showing-completed-daily-goals/m-p/4217622

(been there, done that)

https://community.fitbit.com/t5/Other-Versa-Smartwatches/Versa-miles-circle-not-closing-even-after-m...

(oh, boy)

[MarioDings]

Well, well! I Found the bug!😁😎 (I guess)

For some obscure reason there was a difference between "Main Goal" on the Android phone and the setting of the tracking in the dashboard(browser).

So guys and girls developers and testers, check this out.

@AlejandraFitbit

@RicardoFitbit 

@MarreFitbit 

@AlessFitbit 

[NSJ1991]

Yes I established this over a year ago....it resets itself after 'fixing it'...still no solution. 

[MarioDings]

Sorry @NSJ1991 it's back The android app has a big problem with miles to miles conversion. (Hint: 1mile =1.609344km=1mile).So back to the drawing board. 

Fitbit, let me explain: If I enter a goal of 5 miles, then I mean 5*1.609344 km = 8.04672 km and dont forget that the conversion has happend. And the API transfers 8.04672 km witch is actually 8.04672/1.609344 = 5 miles and not 8.04672 miles.

Reference: User-activity API

Since I am as developer dependend on the API my clockface gives the same WRONG output.

Since fitbit uses the same API also the "today"-app on the fitbit Versa and Sense have the same WRONG output. 

Luckily "only" US-users have this problem.

I'm done.

I wonder if this is a forgotten bug, or is it that nobody cares.

[Kyle_Randall]

Has anyone heard a response on this? 

The issue is still present and it's it's a bit funny that android/Google/Fitbit can't solve a simple conversion issue but also a bit infuriating that we all have to rig our goals to make them appear correctly after like 2 years of this issue.

[PeteMJ]

It's been an issue for the past 3 years. They genuinely do not care.

It's probably 3-4 lines of code, it will be there until they completely overhaul the software, either because they can't be bothered to do it or because their code is such a tangled mess that somehow editing a basic unit conversion error will break the rest of the system.

[jaystylez]

I have the same issue and posted it a few weeks ago for newly purchased inspire 3 which has never worked.

https://community.fitbit.com/t5/Android-App/Inspire-3-is-not-tracking-the-correct-distance-in-kilome...