Android: Fitbit app not displaying maps or splits

[JBuckoloots]

I'm running Android 8 (Oreo) on a Google pixel and I have a Charge 2. The maps always worked fine and the splits did too. Now I simply get nothing. The problem began a month ago, before the OS updated from 7 to 8. I can see there is a GPS signal, because I wait for it to home in on me before I leave for my run and the voice cues at each mile are the same as ever.

[MariamV]

@JBuckoloots thanks for joining us and for reporting this! 

That sounds odd; would you please post a screenshot of what you're describing please? I recommend logging out from your app, restarting your mobile device and then logging back in again. I have found a thread with a similar situation, let me know if this is exactly what's going on with your GPS map. 

I'll be looking forward to your new comments! 

PS. You might have noticed that I moved your post to the Android forum as this was originally posted in the iOS forum. In here you'll find more relevant info related to your inquiry and it also help us to keep the community organized for everyone! 

[JBuckoloots]

Hi Mariam,

  Thanks for the reply. I did as you instructed (and had done so previously) and I'm still getting the same result. Here's a screenshot of the "map" section of the app after a 6mi run this morning. As always, I made sure there was GPS signal before starting my run (it homed right in on me in front of my house) and the voice cues worked at each mile (though I never understood if that was tracked by steps or GPS). At any rate, still no map action.

[Quppa]

@JBuckoloots The bug you're seeing seems to have been introduced with version 2.55 (at least that's when I noticed it). As long as you don't use pause/resume when tracking your exercise, the map will still be visible in the exercise screen later.

[MariamV]

@Quppa thanks for posting here in this thread! @JBuckoloots thank you for the update.  Our Team is currently working hard on a fix. 

Any update related to this bug will be posted in this thread right here. 

Keep an eye on it! 

[Quppa]

@MariamV To be clear, the issue @JBuckoloots reported here only started happening in 2.55 whereas the long-standing pause/resume bug has been present since 2.43. It'd be great if both were fixed at the same time, of course 🙂

[MariamV]

@Quppa I appreciate your follow up with this issue. Rest assured our engineers and devs are working hard on a fix for both these issues. As I state before, please keep an eye on this thread for updates about this. 

Catch you later!