Fitbit App sleep map not updating

[SloMoFred]

My FitBit Charge 6 (and my old Versa 2) doesn't pick up my initial sleep when I sync it with the FitBit app (v 4.52) on my iPhone 13 Pro (iOS 26.0.1).  After syncing, I have to manually update my sleep temporal range.  That has been happening since I started using a FitBit in 2019 so that is my "normal".  Since 10/7/25, the sleep map on the app will not update after my manual update of the sleep range.  Closing and reopening the app doesn't help.  Deleting and reinstalling the app and rebooting both my FitBit and my iPhone doesn't help.  See the attached pix.

10/7/25 - only gives awake, restless, and asleep

10/8/25 - only gives start and stop, no map at all

10/9/25 - sleep started at 11:40pm, map starts at 12:22am

10/10/25 - sleep started at 11:30pm, map starts at 5:36am

10/11/25 - sleep started at 12:33am, map starts at 12:53am

10/12/25 - sleep started at 2:26am, map starts at 3:54am

I track information from the map so I need it to work correctly.  Thanks.

Moderator edit: clarified subject.

[SloMoFred]

Day 26, still happening.  No response from Google/FitBit.  Only responses are from three people having the same problem.

11/4/25 sleep started at 1:17am and the map started at 2:29am.

[SloMoFred]

Day 27, still happening.  No response from Google/FitBit.  Only responses are from three people having the same problem.

11/5/25 Fitbit coughed out the sleep end time and that's all it could manage today.  I set the sleep start time.  Wittle Fitbit did a vewy good job finding the difference.  Awwwwww such a good wittle boy.  $120 for a Fitbit Charge 6 just so it could subtract one time from another?...

[SloMoFred]

Day 28, still happening.  No response from Google/FitBit.  Only responses are from three people having the same problem.

11/6/25 sleep started at 12:56am and the map started at 3:49am.

[SloMoFred]

Day 32, still happening.  No response from Google/FitBit.  Only responses are from three people having the same problem.

11/9/25 sleep started at 1:29am and the map started at 2:33am.

11/10/25 sleep started at 12:50am and the map started at 1:37am.

[SloMoFred]

Day 33, still happening.  No response from Google/FitBit.  Only responses are from three people having the same problem.

11/11/25 sleep started at 12:00am and the map started at 12:59am.

[SloMoFred]

Day 35, still happening.  No response from Google/FitBit.  Only responses are from three people having the same problem.

11/13/25 sleep started at 1:00am and the map started at 1:44am.

[Seniorrookie]

Same here up to two nights ago and the sleep timeline still won’t update after updating the start time like it used to. The Charge 6 has worked wonderfully for me up to around June this year. After that all I seem to be doing is troubleshooting. Anyways have since moved to a different watch. Hope this problem gets addressed soon for all those affected.

[SloMoFred]

Day 37, still happening.  No response from Google/FitBit.  Only responses are from three people having the same problem.

The 11/15/25 map split in two.  The first part ended at 5:49am and the second part started at 7:03am.  I was wearing the watch the entire time so there should be solid data, asleep or awake, from 1:50am to 12:31pm.  Heaven forbid you get up to take a piss middle of the night and then have trouble falling back asleep...  Nope, Fitbit has a rule that that's not allowed...

[ShahrokhSon]

This sucks I’ve been having the same problem you can’t edit your sleep, but there timeline is not updating. 

[SloMoFred]

Day 38, still happening.  No response from Google/FitBit.  Only responses are from four people having the same problem.

11/16/25 sleep started at 11:34pm and the map started at 4:40am.

[SloMoFred]

Day 39, still happening.  No response from Google/FitBit.  Only responses are from four people having the same problem.  I went to submit a trouble ticket on the Google/Fitbit website, fought through the dead links, circular logic, and bureaucracy, and was finally able to submit the ticket asking for a call.  The website said I would receive the call within five minutes.  That was almost four hours ago so I guess that trouble ticket submission page is just another "stunt" like this community page to make us think Google cares about customer service.

11/17/25 sleep started at 1:06am and the map started at 3:07am.

[SloMoFred]

Day 40, still happening.  No response from Google/FitBit.  Only responses are from four people having the same problem.

11/18/25 sleep started at 2:02am and the map started at 2:55am.

[SloMoFred]

Day 41, still happening.  No response from Google/FitBit.  Only responses are from four people having the same problem.

11/19/25 sleep started at 1:25am and the map started at 5:09am.

[SloMoFred]

Day 42, still happening.  No response from Google/FitBit.  Only responses are from four people having the same problem.

11/20/25 sleep started at 11:41pm and the map started at 2:53am.

[SloMoFred]

Day 48, still happening.  No response from Google/FitBit.  Only responses are from four people having the same problem.

11/26/25 sleep started at 1:16am and the map started at 1:57am.

Day 48

[SloMoFred]

Day 49, still happening.  No response from Google/FitBit.  Only responses are from four people having the same problem.

11/27/25 sleep started at 2:36am and the map started at 4:27am.