Charge 2 - no exercise showing on app

[DC_11]

My app has stopped recognising any activity. Last weekend everything was working fine then 2 days later my tracker is showing calories burnt after a class but on syncing to the app…no exercise registers.  I have done all the recommended stuff…opening/closing/deleting apps and tracker and still nothing. 

Does anyone have any suggestions/ideas/advice please?

[Rtkat3]

There must be something wrong on their end or else they would've gotten it fixed by now.

Do you or any of your fellow moderators have anything to comment on this @JuanFitbit?

[JuanFitbit]

Hi everybody! Thank you for your messages and information. Our team is on top of this and working on a long term solution. 

Hopefully this gets published soon.  
We'll be updating the thread as soon as we get more info

[jimblock94]

This is never going to happen. It’s been months.
Sent from my iPhone

[BDoor]

I tend to agree of no fix but there is a 4.38 version, maybe?  Tried to get a bug fix on any of the version on the inter-web but no luck, so, just see if any feedback on this latest version.

[Chris2346]

Not only has it stopped syncing but NOW when you manually start it, it does not show me any info for the few seconds afterwords. I hit stop to end activity and it goes back to the "workout" I picked. No final calories burned or max heartrate. It shows NOTHING! 

[Rtkat3]

I have not seen anything in the Fitbit Community on if anyone has been having problems with the latest Fitbit Charge model.

[LZeeW]

@Rtkat3   I browse nearly all the forums regularly.  This seem to be an issue with the Charge 2, not the Charge 6.  The two models have very different operating systems.  I haven't seen any posts about this issue with the Charge 3, 4, or 5, either.

[Rtkat3]

I think the website mentioned that Charge 6 is the latest Fitbit Charge model.

[JuanFitbit]

Hi everybody! Thank you for your  messages

@Rtkat3 , you are right, the latest Charge model is the Charge 6. 

@all Our team has identify that this issue is being caused by the Fitbit app and not by any Fitbit device specifically! 
They are working on a solution for this. 
Hopefully we don't need to wait longer . 

[Rtkat3]

Thanks for the update @JuanFitbit. Keep us posted on when it is resolved.