Infinite Spinner for GPS Maps

[DerrickS]

Fitbit Update 9/19/16

This issue has been resolved with the release of iOS App version 2.27. Click here to update your App if you haven't already.

Thanks you for everybody's patience while we worked this one out!

Fitbit Update 8/8/2016

It was recently brought to our attention that some users are seeing an infinite spinner on the iOS App for GPS workouts that are longer than 1.5 hours. This is a known issue that our team is currently working to fix.

As a short-term workaround, you can still see the GPS maps for your longer workouts on your Fitbit.com activity log while a fix is being worked out.

[steve43040]

I have 2,25. And maps for long runs (over 18 miles ) do not load to app. They r on the web version help!

[JKLondon]

Same here. Last update seemed to fix for a while but now back to square one with blank maps for all long rides. I notice data spinner stops while app is trying to load - makes me wonder if app cannot handle large gps files and gives up. Strava is fine.

[steve43040]

Yes my problem is big filed .... Long runs over 18 miles

[JKLondon]

So just did a 70km ride and no map shows. Advertised feature clearly doesn't work. Using 2.25 (which erased all my historic app maps on installation). Come on Fitbit - fix the problem.

[steve43040]

Did not loose history with 2.25 but now maps for long runs not loading to app Fitbit we all need this fixed

[JKLondon]

35km ride today and got the map in seconds. Still no sign of yesterday's 70km ride map - just a grey panel with spinner.

[steve43040]

Still waiting in fix
I get maps for short runs but
Just gray panel with spinner for long runs.

Still waiting
When will we know when this will be fixed ?

[steve43040]

No success still need fixing
Using current update 2.25

[DerrickS]

@steve43040 @JKLondon @steve43040 This is a known problem with the app that our engineers are currently working out.

If the duration of a workout is over 1.5 hours, the map will not load on the App and you'll see an infinite spinner.

The good news is that you should still able to see the GPS maps for your long workouts on your Fitbit.com activity log while a fix is being worked out.

I'll keep you posted with updates as they come in.

[steve43040]

Hi,

Do know when this will be fixed ?

I need to have map on app for my running team. If this cannot be fixed I may meet to go back to a garmin

Thanks Steve

Sent from my iPhone

[JKLondon]

Thanks for update.  Good to know that the problem is at least acknowledged.  It would be good if the engineers could also fix the Surge's tendancy to 'end' an exercise that has been paused.  Random contacts / brushes across touchscreen whilst paused seems to trigger a switch to summary screen with no means of restarting. It's really frustrating and means I have to merge the now separated exercises together using TextEdit and import to Strava to see complete ride. Alternatively the engineers could add an embedded merge facility to the app / web dash so completed exercise can be viewed in Fitbit (assuming the map ever loads...) 

[steve43040]

Yes in addition to fixing loading the map from a long run ,,, it would be nice to restart the monitoring of an exercise when it is pauses. I have had nine stop 2x in the middle is a run

Please fix these.........

Thanks
Steve

[leonnyan]

Me too. Commenting so I can track progress.

[JKLondon]

Installed the new 2.26 update today. Still doesn't work.

[TunaBoy2]

I have been using the track exercise on my Iphone to track my walks for the past few months.  I went to the website to have a look back at the maps on my exercises. But they were not showing up. I went back to the iphone and clicked sync. It will not sync.  I do have a charge hr that appears to sync an exercise.

[DerrickS]

@TunaBoy2 Just a heads up, I've merged your post into this thread where users are experiencing the same thing.

Users who are going on longer GPS workouts are experiencing an infinite spinner on the iOS App, but can see their workouts on Fitbit.com.

This is a known issue that our team is working to resolve and I'll post updates about this issue in my lead-in post as they come in.

[leonnyan]

An update. I am now seeing maps on my iPhone app for longer hikes. I have a 3:22 from this past weekend that maps.

But, I still have longer ones that do not map in the app (7:00+, 3:58). I do not know where the cut line is if it is duration based, but I am still experience unmapped exercises of long duration.

--Leon

[DerrickS]

This issue has been resolved with the release of iOS App version 2.27. Click here to update your App if you haven't already.

Thanks you for everybody's patience while we worked this one out!

[leonnyan]

I still have two maps that don't load and now I'm not sure why. One is 12.78 miles, another is 8.31 miles - both while traveling in Yosemite. I have other hikes/walks of similar distances (and durations) that do load a map so am not sure what might be causing this now.

--Leon