Dots in maps Pace/Lap have the wrong distances

[Timmy0767]

The issue appear to be resolved in the text laps but the photo pacing still shows as KM 

example i ran 1.75mi with my dog and there are two dots after the update on the map of the run.  The actual laps do list the 1.0 and the .75 accurately

Moderator edit:  updated subject for clarity

[Nattyem]

This is also my experience. The lap times are back to miles, but the markers on the map are in km.

[JuanFitbit]

@Timmy0767 @Nattyem , Thank you for your messages and for confirming that the issue with the laps/splits distances was solved. 

I moved your posts over here to address the new symptom. To keep the Community in order and for everyone else to have a better overlook at this new issue. So we all can avoid misunderstandings or confusion with the previous issue. 
I've informed Support and they'll be looking into the issue with the map. They'll work on a solution for it.

I'll be updating the thread as soon as we receive further info. 

[Timmy0767]

@JuanFitbit the update corrected the chart view of running mileage/time

The map view is still putting intervals at KM. Additionally, bicycle ride speed is listing the KPH value as MPH.

[LFortier]

The problem is still the same. It has not been fixed. In the app I see the pace in miles now, both in list form and on the map, but when I export it to My Maps it still breaks it down in kms. The first pictures shows that the app is clocking miles at a mile distance. The second picture shows the mile times, and the third picture shows how it breaks it down totally differently on the export. 

 

 

 

 

[JuanFitbit]

@Timmy0767 @LFortier , Thank you for your messages and screenshots. 

We have now this thread where we will be following up with the new issue. 

The info has been passed to our team so that they get a look at this.

[Timmy0767]

Speed on bike rides is listed in KPH not MPH

example: 

 

 

[JuanFitbit]

Hi everybody ! Thank you for your patience and help. 

Our team has worked a fix for this. It will be available on the next app update. 

Please keep an eye open for the update. 

Please let us know over here, if with the 4.45 update the issue got solved or still persists.