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?

[m_star011]

ANyone actually contacted Google and find out whats going on? its been months and months.  Not sure if other fitbits have same issue.

[Rtkat3]

I think someone did. I don't think the moderators have noticed any other complaints with the other Fitbit models.

[Ellen511]

Yes, I have called customer service 3x. Each time they claimed to not be aware of the issue. The moderator on the chat is the first time I’ve seen anyone from Google acknowledge the issue.

[m_star011]

Same here i wonder why they don't see the issue.  I am confused why google don't resolve it asap.  

[helenkay23]

Hello, I’ve been diverted to this thread from the moderator as there was a similar thread with activity issues, particularly with the charge 2 device.

I reported the issue to Fitbit/Google support a few times and they advised me there’s no timescale on the resolve and they are ‘looking into it’.

To me it looks to be an app issue as I tried everything - reset watch, updated app and iPhone, reinstalled the app, re added watch device, I even tried to add a new charge 2 device as I had a spare never used and the device required an update which wouldn’t work. My charge 2 is syncing to the app and looks to be recording step count etc but not logging exercises or walks. I’m also unable to add manually as they disappear. I’m also signed in with Google account.

Still hope to have the issue fixed as I will be giving my charge 2 device to a family member mainly to record steps and hopefully walks.

Moderator edit: formatting

[Rtkat3]

I just got an update to my Fitbit from the Google Play store. How does one check to see what version it is anyway?

[joggerj]

On Android, if you long press on the app icon, it will show you a menu where you can click on app information and the version at the bottom.  This may be different on different Android versions though.

I don't think there's any new update that's supposed to fix the ongoing problem yet, else we would have been told.  I'd just assume it's not fixed yet.

[Rtkat3]

Mine is at 4.34.1 after I had to go to settings to find out.

---

The Google Play Store has released the 4.35 version of Fitbit which I updated.

[m_star011]

did it work?

[Rtkat3]

I haven't tracked an exercise yet.

[CaptKen]

The issue we've been complaining about has not been fixed with 4.35.

[BDoor]

Update: shifted to newest message and saw the SAD news that 4.35 ver did NOT fix.  Guess this is the way to phase out the old reliable Charge 2 out.  🤔

Watching this as do love the charge 2 as my multiple charge 3's went to dark mode no op.  Wondering if the newest version, 4.35, fixed the exercise sync problem for users.  Little afraid if new version has even more problems.

Cheers.

[Rtkat3]

The previous user said that there hasn't been any improvements to the glitch. It is still manually tracking walks around the neighborhood on my part.

[Brunow_110]

No fixes at all. Tried to track exercises starting them on the watch...none of them showed in the app.

[ruffianfan]

This is after downloading an update to the app?
No surprise. Thanks

[PinzLindz]

I also have the 4.35 version downloaded and it has not been recognizing any of my activities since...I'm not even sure. I'm trying to figure out if I can get credit toward a replacement?

[m_star011]

Anybody know if the charge 3,4,5 have same issue? anyone tried? 

[Chris2346]

Now no activity is recignized, not walks by gps or manually started activity. 

Moderator Edit: Word choice

[JuanFitbit]

Hi everybody! Thank you for your messages and further feedback. 

I'll pass your info along so that our team knows about the new symptoms and they continue working on a solution for this. 
They are already aware. 

Hopefully this gets solved soon. 

Keep in mind, that this is an app issue and is independent from the device model. 

[Rtkat3]

Thanks for the update.