Fitbit app loses total sleep if extra sleep removed

[narrlv]

1. This has occurred twice in a few days, and appears to be bug in latest 4.41 Fitbit app on Android.
   The problem comes when you get extra sleep recorded, besides the main night session. It will have simplified information about restlessness, not the full analysis which the main sleep recording has.
2. Normally you can use the upper right vertical 3-dot menu to delete this extra sleep, if it wasn't valid (perhaps sitting too quietly rather than taking a nap). When you choose the sleep to delete, it disappears, and its extra value is subtracted from total sleep.
3. But on 4.41, if you do this removal of extra sleep, then the time for sleeping in the Sleep details of the app now shows 0min out of 8h goal (or your goal if different), and the Sleep duration on the top level of thet app says No data, both of these instead of the time which should come from the regular sleep interval which is still present with its details.
4. The bug may not begin with 4.41, as there have been several Android Fitbit app updates in recent days, but it recent, with a few weeks, as this deletion and proper recalculation worked fine when I have used it not long ago, before.

I've just been on the phone with Fitbit support, and they have a good report on exactly what occurs, etc.. I'm informed that there is already a 4.42 further update ready, which hasn't arrived at my device yet to try. If it doesn't fix the problem, I'll report again of course. We don't know if it has a fix for this problem intended.

We ran through a procedure during the call, but this doesn't seem relevant beyond what we saw from it. So as ever, patience (is a virtue, Confucius is reported to have said), and that should get a repair before long. I've been quite happy otherwise with latest firmware and Fitbit app, and certainly was with how this support call went.

Apparently both chat and calls are provided even if you don't have premium, by working down through the steps which are not problematic, from this main link.

[RiekoC]

Hello @narrlv 

Thank you for sharing this issue and your communications with Fitbit support about the bug. 

Hopefully, the fix will be included in the next app update.