10-31-2017
10:48
- last edited on
11-02-2017
07:39
by
MarcoGFitbit
10-31-2017
10:48
- last edited on
11-02-2017
07:39
by
MarcoGFitbit
Hey guys, wonder if anyone can help.
Recently i have noticed that on a sync my active mins get synced to the app (for example today) if registered 66 mins active when i manually synced the data. When i did a second sync later in the data i noticed that the active mins was then set to zero.
I have screenshots for both syncs if its needed as proof.
Fitbit's website also says zero now, where was the app DID say 66 mins earlyer today.
Bug?
Moderator Edit: Clarified Subject.
Best Answer11-02-2017 07:41
Community Moderator Alumni are previous members of the Moderation Team, which ensures conversations are friendly, factual, and on-topic. Moderators are here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
11-02-2017 07:41
Hello @FailCascade, have a warm welcome to the Fitbit Community, it's great to have you on board. ![]()
Thanks for bringing this to my attention, is this the first time you've experienced this issue? If so, please update the Fitbit app as we have recently released a new version (2.42) and monitor it for the next 24 hours to check if Active Minutes disappear again. If they do, please take a screenshot and reply to me with it so I can check this further.
I hope this can be helpful, if there's anything else I can do for you, please feel free to reply as well.
Best Answer11-02-2017 09:51
11-02-2017 09:51
My Charge 2 started doing this on October 25th It took until today to be told it's a known issue with the app and they are working on it...
Best Answer11-04-2017 05:47
Community Moderator Alumni are previous members of the Moderation Team, which ensures conversations are friendly, factual, and on-topic. Moderators are here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
11-04-2017 05:47
Hello @BuckeyeRunner, I hope you're doing well, thanks for joining the conversation. ![]()
I appreciate you have shared with me the response provided by our Support Team. Indeed, this has been cataloged as a bug and our team is currently working towards a prompt and proper solution for it.
Thanks for your patience and understanding, in the meantime, if there's anything else I can do for you, please feel free to reply.
Best Answer