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! 

[ThunderRun]

@Colinm39 thanks for this tip! I'll try it out.

[spectre1989]

I seem to get this when syncing fails due to network conditions, then when I try again later the map is gone. I think the app devs need to cache the map data locally until the push to server is successful. Really annoying, I just set what was likely a new 5K PB, but won't get it on strava because the map disappeared 😞

[PiLesley]

Hi,

2.49 not in the UK yet 14:00 hrs Thursday 18th .... Waiting....

[Quppa]

I got 2.49 earlier today. The bug seems not to have been fixed.

Interestingly it seems to be behaving slightly differently now - I don't even see the map/summary of the exercise and get taken back to the Fitbit dashboard immediately. No record of it is stored.

[Kelsen]

So frustrating!!! I went for my first run last week, it logged the run and the information was very valuable for me being a starter.

I went for a 50' run today and no map or pace data is showing while i started the tracker.

I'm pretty sure it showed the map when I paused. And after tapping 'Finish' it's all gone.

How is this possible!

[PiLesley]

I agree. Disappointing. Nothing shows at all now. No data at all, not just no map, nothing.

The exercise didn't happen!

Back to 2.42 me things.

[Colinm39]

I have just tested 2.49 and no change for me.  Not resuming doesn't save maps or data but a single pause and hold Finish works as for 2.48.

So the non GPS users have too wait for the next upgrade.

[Quppa]

2.49 also fails to fix the issue where pace is initially shown as 0:00 after finishing.

[Colinm39]

Because we are dealing with a "bug" we need to bring some humour into this issue.. For the younger Fitbitters this was coined "bug" in the 1940's.. 71 years ago...

A typical version of the story is: In 1946, when Grace Hopper was released from active duty, she joined the Harvard Faculty at the Computation Laboratory where she continued her work on the Mark II and Mark III. Operators traced an error in the Mark II to a moth trapped in a relay, coining the term bug.

For the sake of all of the non GPS tracker users lets hope a fix is coming soon.  Looking through the last few weeks we are getting new App every 2 weeks approx.. So on the season change we will see another attempt at fixing something.

[siris10]

This ain't getting fixed any time soon I guess - this is their reply to my latest email 

Hi John,



Thank you for your feedback and response. We apologize for the delay in our reply.



As you know, our engineers are now aware of this issue and looking into similar reports. However, we still do not have a timeline for when this will be resolved. We sincerely apologize for the inconvenience.



Thank you for your continued patience in this matter. 



Sincerely,

Danny L and the Fitbit Team

Sent from my Samsung Galaxy smartphone.

[Kelsen]

What an arrogance. Looks like they have more important things to do, well in that case, I'll be tracking my runs with runtastic. An app that actually WORKS. 

[Markd08]

Phone: Samsung Galaxy S5

App version: 2.49 (2183128)

Missing metrics: Map, splits, pace, total distance

Date/time: Finish date/time appox. 5/22/2017 12:40PM

Paused and finished run, fitbit app appeared to get stuck on green motivational screen that appears after pressing and holding finish. Had to reopen the app to see anything

[Kelsen]

Hi guys,

It looks like for me, It's tracking my  run if I don't PAUSE when I go stretch.
So without pausing, it tracks the run. If I pause, everything is gone.

[Rich_Laue]

That is correct, as mentioned many times above. Do not paise and resume, you must press stop after a pause. 

At least until it gets fixed.

[Kelsen]

I didn't read all 25 pages, but 5 at least 🙂 Someone should add it to the first post as 'temporary fix'.

[PiLesley]

Don't waste your time trying to get to the bottom of this.

We did that weeks ago.

Fitbit bug.

Workaround for the time being is only pause finish, never pause continue.

Read back over posts

[Markd08]

Pause finish is not a work around. That's all I do and that's how I lost
the data.

[Rich_Laue]

Im sorry your one of the few that the last app update caused more problems.

It does seem to be a workaround for most people, this promblem affected almost everry Android user, then a fix was released that did help many users. However it soon was discovered that the update also caused aditional problems for a few users. Yes i could search for this post. However with an unknown amount of threads on this subject spread around multiple hardware and software forums, this is strickly a software unrelated to any tracker hardware, Im not going to search and weed through the results.

This update was beta tested before being released, but apparently not v all types affected phones or configurations where tested.

[PiLesley]

Uninstall fitbit.

Go to apkmirror.

Install 2.42.

Everything works perfectly.

Then wait until proper fix available.

Is my suggestion

[Colinm39]

I don't want to cloud this issue with another I have found.. In this link I have tested and shown how erratic the Pace Graph is in MobileRun.  So while many are examining their saved maps I'm interested to see if others are experiencing this.

One of the tests shows concurrency with Connected GPS and parallel to that I have the Surge to show that the GPS was stable.. Using the Connected GPS Blaze shows a reasonable graph and activiated at the same time ios the MobileRun sawtooth graph....So very erratic graph