Android Fitbit app backs out before showing me details on my recent long bike rides

[JonSpencerX]

I cycled 101 km today. I cycled about 87 km the other day. And 93 km 3 days before that. If I try to view any of these 3 exercises in the Fitbit app on Android, it backs me out to the previous screen.

I can look at older long-ride maps, going back several weeks. I can look at recent shorter ride (and walk) maps. But these 3 will not load. And the second bike ride did not port over to Runkeeper (which is something that I have set up and has always worked before), but the first and third of these rides did so without a problem.

Could this have anything to do with the changes Google is making to the Timeline being accessible only on Google Maps' mobile app? Or what is going on?

(I posted about this the other day but somehow it wound up in the Fitbit Ace forum so the topic got "locked". I've no idea how it wound up there. Let's hope this topic doesn't suffer a similar fate!) 

[JonSpencerX]

This is really getting me down. Still can't view my maps, and today's 105 km ride won't load in Fitbit, nor was it ported over to Runkeeper, which only shows the first 2 km. What the heck have you done with my data? This is depressing. This is the main reason I use Fitbit and Runkeeper. 

 

[Gr4ndp4]

Hi, @JonSpencerX welcome, how did you start the bike ride recording? did you use the exercise>bike ride icons on your Fitbit (please let us know which Fitbit you are using) or did you rely on the auto-recognize feature? If the latter note this does not engage GPS, essential for a map.

I regret I'm not familiar with "Runkeeper"

I hope this helps.

Cheers

[Triletics]

@Gr4ndp4 there is a bug in the new app for long GPS activities. I see the same issue for my long runs. The app does two things - either backs out to the main screen or crashes. Usually, first time an activity is opened, it backs out. Second time - app crashes like here:

Also, this is how long it takes to open it (the app is painfully slow when opening longer GPS activities but that was always the case).

[JonSpencerX]

I click on the "bike" icon on my Charge 5, and then the Start icon. As I
have since I started using it about 18 months ago.

I'm confident that there IS a map underlying the calculations of distance
and calories, because sometimes (always except twice now) it also exports
it to Runkeeper, a separate app that Fitbit integrates with.

The problem appears to be that the Fitbit app (at least on Android) is
unable to call up the map because it reaches some sort of "timeout" limit.

[Gr4ndp4]

Hi, @JonSpencerX thanks for the feedback, may I suggest you review the GPS settings on your Charge 5? The options are built-in, dynamic & phone.  How do I use GPS on my Fitbit device? - Fitbit Help Center explains the differences. In the past Dynamic failed to engage the alternative GPS, in my experience the best setting is to use "Phone", a larger battery & antenna. If you are presently using built-in or dynamic this may explain the lack of consistency. 

Try using "Phone" & let us know how you get on.

Cheers

[Triletics]

@Gr4ndp4 there is a bug in the app. See my reply. It's recent because it all worked before. Past activities with very long GPS routes crash the app. I posted an animated GIF here showing the problem. When trying to load the map the app either returns to the previous screen or (on the second attempt) crashes.

[JonSpencerX]

I've had it set for Phone since my early days with the Fitbit, since anything else would drain the battery long before my ride would be over.