03-21-2017 12:42 - edited 04-24-2017 13:39
03-21-2017 12:42 - edited 04-24-2017 13:39
Fitbit Update 04/24/2017: Hi all -- As this has been reported as resolved with the Fitbit app update, version 2.47, I am closing this thread.
If you come across any other instances of this in the future, please create a new thread and use this one as a reference. Thanks to everyone who reported this, tried the update and confirmed that the markers are displaying as expected.
Fitbit Update 03/21/2017: Our team is aware of a bug where users running Android 7.0 Nougat experience the popup markers overlapping in the full-screen view of the following graphs: Heart rate, water, weight, steps, calories, floors, distance, and active minutes.
Our team currently working on getting this issue resolved as quickly as possible. I appreciate your time in reporting this issue and am looking forward to providing an update as soon as I can. More to come!
04-05-2017 22:42
04-05-2017 22:42
With the last update all graphs have been fixed except the restless/awake one!
Thanks FitBit team!
04-06-2017 01:54
04-06-2017 01:54
RHR popup Markers now working with App 2.46.
04-06-2017 10:50
04-06-2017 10:50
Hello moderator, can you get this issue resolved, I got the new update, loged in on my android app, and when I go on to the sleep pattern screen and hit the graph to seee the whole layout, I still cannot click on one or all of the different lines, meaning awake time, restless, and sleep. I had this working when we had the update before this new one, why is it no longer avalible, how are we going to tell what time we got up in the middle of the night, also restless, come on how much does it take to clear this up.
John.B
04-20-2017 05:08 - edited 04-20-2017 05:14
04-20-2017 05:08 - edited 04-20-2017 05:14
Version 2.47 Android App now has the popups.. and at the top.. Well done.. Here is the link
04-24-2017 13:40
04-24-2017 13:40
Fitbit Update 04/24/2017: Hi all -- As this has been reported as resolved with the Fitbit app update, version 2.47, I am closing this thread.
If you come across any other instances of this in the future, please create a new thread and use this one as a reference. Thanks to everyone who reported this, tried the update and confirmed that the markers are displaying as expected.