Workouts Started on Charge 5 NOT Syncing to Fitbit App on iPhone

[jjfeigal]

Since August 31 workouts started on my Charge 5 do NOT sync to the Fitbit app. After ending a workout on the Charge 5 I can see the workout days updated on the Fitbit. After syncing with the Fitbit app, workout days are not available in the app and no details about the workout are available. My workouts are always Walks. I have an iPhone 14 Pro and have been running iOS 17.6 but I updated to 17.7 yesterday. I updated the Fitbit app after tonight’s walk, but no workouts show up even though the app info in the Apple App Store indicated there were bug fixes.

[christekm1]

Hi, I observed the same issue with my charge 5 about two weeks ago. If I manually add the activity to my dashboard, it does show many of the statistics although for some reason it doesn’t accumulate the minutes by zone. It just shows the graph but not the summary.

I’m hoping that Fitbit is watching this chain of discussion because this is the second or third one I’ve seen on this topic with no response from Fitbit…... No surprise.  😞

[RiekoC · Accepted solution]

Hello @jjfeigal & @christekm1 

There is an issue on the Fitbit side that affects our ability to see exercise data in the Fitbit app. A Moderator posted on 12 Sep 2024 acknowledging the syncing issues and data transfer errors. He said that the team is working on identifying a resolution as quickly as possible.

For now, there's no troubleshooting that we can do on our side.

[KateJellyfishhh]

Was this rectified? I have an old charge 2 and iPhone 12 and if I start a workout from the watch itself it doesn’t load to the app, showing that I haven’t done any exercise that day. I did an intense HIIT class last week but didn’t start from the watch to see if it would auto log the workout and it thought I’d been for a walk instead…

[RiekoC]

Hello @KateJellyfishhh 

The earlier Moderator posts I read on issue indicated that the next app update, version 4.27/4.27.1 would fix the problem. However, I've seen users reporting that they still experience the problem even after updating their app to version 4.27/4.27.1. I believe I saw a Moderator post in a thread about this problem stating that they will inform Support that users are still having this problem even after installing the update.

At this point, there isn't any troubleshooting to recommended since the issue is on the Fitbit side.