MobileRun missing data after pausing - Android 2.43+

[AlessFitbit]

Fitbit Update: 9/26/17

Hello, everyone! I wanted to make it known that I haven't forgotten about this issue with MobileRun. Our team is aware of this ongoing problem, however, I don't have a timeline for when there will be a fix available. I understand many of you are frustrated with this feature, and I hope to give you all more information soon. Thanks for your continued patience! 

Just to be clear, this thread is for the MobileRun issue for when you initiate a Run/Walk, if you 'Pause' your activity and then 'Resume' after you finish, you will not see your map or some of your exercise data. Alternatively, this does not happen if you 'Pause' and 'Finish' your Run/Walk right away. 

---

Fitbit Update: 7/20/17

Thanks everyone for providing the information requested about this MobileRun issue. It appears since the Android app version 2.43, users who initiate a MobileRun on their devices and later pause it at some point will not have all the data saved when syncing afterward. This data can include the map and distance data. 

I really appreciate your cooperation and patience while our team works towards a resolution. I know many of you have been active on this thread and I want to make sure you know all your input has been very helpful in determining the factors. I will continue to update this thread when there is more information available. Thanks again for your help! 

[siris10]

I did indeed hit pause - right before a mamouth hill! I read all 19 pages of this thread and tried it again while out walking my dog and it recorded it fine... at least I know not to hit pause when I'm out running now

[Shelley919]

Same issue here. Galaxy S7, Android. I record my walk live in the app and then when I finish I see the map and results. Then when it syncs, it disappears and I can never see it again. So then I go in and manually log the walk I just did, otherwise it doesn't know that I exercised that day. 😞

[estegiro]

The same thing is happening to my phone since I updated the app about 2 weeks ago. This is frustrating as seeing the map is one of my favorite features. Come on fitbit, don't forget your Android users. 

[Rich_Laue]

Hello @estegiro did you at any time durring hit paise and then resume? 

Also could you help out @ErickFitbit by answering his questions?

https://community.fitbit.com/t5/Android-App/Missing-MobileRun-map-pace-data-Android-2-44/m-p/1957123...

[Colinm39]

@Rich_Laue Over the last few weeks I have randomly tested my GPS.

Today I was brave and did simultaneous tests with Blaze Connected GPS, MobileRun and MapMyRun and when I finished I received my 3 plots.

But, as you post, for MobileRun you MUST never pause and resume, just the one pause at the end and hold finish and get the green splash screen.

[estegiro]

Hello @ErickFitbit,

The issue began after the most recent update. It worked perfectly fine before the update. I could pause during my hike and resume without my map disappearing in the end. 

I have a Samsung S7. It occurred when using MobileRun for a hike on 04/30/2017 at 10:14am and ending the hike at around 3:00pm. I also had this issue occur on my last hike on 04/23/2017. 

[siris10]

It worked tonight, at least not pausing is a work around until fitbit sort the issue out... not ideal as it was only a little 5k run and if I go out for 10-15k I will stop for a breather. I also used the Strava app at the same time which worked fine however I like the heart rate to show so I can monitor my cardio improvements which Strava does not do with a Fitbit

[Chrissylee842]

I've had the same exact issues.  I will go to track a run, press complete workout at the end and I can see the map, splits etc and then when I go back into the app, it has all disappeared and been replaced by the basic 'run' in the exercise log.  

I have played with waiting after I'm done and not backing out of the screen or going to a new app, sometimes it works and sometimes it doesn't.  Its like an annoying game of Chance.  

I have just started using Runkeeper so I have an accurate view of my routes.  Its a bummer, because I had been using the Fitbit feature for about a year and up until about 2 months ago had no issues and loved it.

[siris10]

Have you paused the app during your run? This is what is causing the issue, since I've not paused mid run it records them fine and transfers the info to Strava.


Sent from my Samsung Galaxy smartphone.

[Chrissylee842]

Thanks!

That is both interesting and annoying that that function would cause this - hopefully they are working on a fix.  

That would explain it though - since sometimes it records and sometimes it doesn't and I occasionally do use the pause function.  

[PiLesley]

IF they are working on it, since 9th March, we aren't in the loop as to when to expect this fundamental fix

Sent by LeSLeY

[siris10]

If you hit pause you may as well complete the run/walk and then restart it. It's a pain on the **ahem** but Fitbit are apparently working on it however it's been two months now 😔


Sent from my Samsung Galaxy smartphone.

[PiLesley]

Just got app update 2.48.
Anybody tried it?
I'll try in the next couple of hours or so

Sent by LeSLeY

[Colinm39]

@PiLesley  No change... I just did some tests and the Pause Finish worked, but the Pause Resume x 1 pause/resume and by 2 pauses and resume showed the map but no sync..

You only need to do a test for more than a minute and when you finish you will get a message like "Are you teasing me" or similar..

Therefore no loss of effort..  The Pause Finish has always worked for me..

---

@PiLesley wrote:
Just got app update 2.48.
Anybody tried it?
I'll try in the next couple of hours or so

Sent by LeSLeY

---

[PiLesley]

Well that's just great!
My hopes dashed!
You'd think by now we'd deserve a bit of respect and feedback on this issue wouldn't you?
Soooo disappointing.

Sent by LeSLeY

[Colinm39]

@PiLesleyI agree with you and I have been a Fitbitter for nearly 6 years and had my disappointments with the wrist based trackers..

But this is more fundamental, because we are talking about the Android for me.. I'm not sure if the Windows Phone or the Apple have the same problem.

What is confusing the issue is those like me, who only have the failure when I resume and their are others who have the failure using both methods.

I have no issues with MapMyRun or using Connected GPS on the Blaze. Only the East/West gaining distance and pace in the Southern Hemisphere on the Blaze..

---

@PiLesley wrote:
Well that's just great!
My hopes dashed!
You'd think by now we'd deserve a bit of respect and feedback on this issue wouldn't you?
Soooo disappointing.

Sent by LeSLeY

---

[PiLesley]

I'm a three year youngster!
I know an apple use, no problem.
Don't think any/many Windows phones supported.
This is all very bad craic as they say in the North East

Sent by LeSLeY

[Quppa]

2.48 hasn't fixed the problem for me, either. Pause/resume/pause/finish caused the log to be lost, just as before.

[PiLesley]

I'm so disheartened by it all

Sent by LeSLeY

[andreamhall]

What is the make and model of your mobile device? Google Pixel.

What version of the Android app are you currently running (Account > Help)? Fitbit Version 2.48, Android 7.1.2

What metric is no longer showing: Is it just pace? Is it just the GPS mapping? Is it both? When I finish a run I can see the map, distance, splits, just like I used to be able to see later when I looked at a previous run. But now it disappears and all I can see is my heart rate, calories and steps. 

Give me the date and time that this event occurred. May 5th, May 1st, and April 28th. The last run I can see the map for is from April 18th.