01-05-2019 11:00
01-05-2019 11:00
I'm writing this like I would do a bug for my software team. Clearly the notification handling system is broken. I can't tell if it's at the app/server end or at the watch firmware end, but I believe it's the former.
Here's how to reproduce it:
I believe this to be an Android app issue because if I force stop (using Settings) and re-start the FitBit app, I start receiving notifications again.
Other things that I noticed:
These two observations lead me to believe that there may be issues in the watch firmware side too. It depends on how you implemented notifications:
01-05-2019 12:53
01-05-2019 12:53
On those 2-3 days have you had any updates to your phones OS are the Fitbit app?
Do you get notifications on your phones lock screen.
Have you restarted the phone and the ionic, both have fixed the problem at times for me.
Is your phone on the compatability list?
Have you checked the notification settings on the Fitbit app?
Fitbit app permissions?
Logged out/in on the Fitbit app?
Turnedvoff notifications in the Fitbit app, then re-enabled? This should force the phone to request permissions.
01-05-2019 13:02
01-05-2019 13:02
On those 2-3 days have you had any updates to your phones OS are the Fitbit app?
No OS updates, some non-FitBit app updates (e.g., Twitter, Instagram, etc.), don't think I had any FitBit app updates
Do you get notifications on your phones lock screen.
Yes
Have you restarted the phone and the ionic, both have fixed the problem at times for me.
Are you seriously recommending I do this, every 2-3 days? If this is a resolution of the problem, you need to have your 'Community Legend' status re-evaluated. It's an inane answer and certainly not befitting a manufacturer claiming the feature.
Is your phone on the compatability list?
Yes, it's on the list.
Have you checked the notification settings on the Fitbit app?
Yes, they're enabled
Fitbit app permissions?
Yes
Logged out/in on the Fitbit app?
No, not during the 2-3 days
Turnedvoff notifications in the Fitbit app, then re-enabled? This should force the phone to request permissions.
Are you seriously recommending this as an on-going solution?
01-05-2019 15:58
01-05-2019 15:58
No I'm not recommending doing this every 2-3 days.
I assume your asking because notifications are not working and you want to find out why?
Your phone and your Fitbit are simply computers and occasionally hardware will lock up and a restart is the easiest way to fix this. Considering Android still has memory management problems a restart is required at least once a week
But I'm seriously giving up since I have no idea what phone you are having issues with and can only guess at what to check.
01-05-2019 18:22 - edited 01-05-2019 18:25
01-05-2019 18:22 - edited 01-05-2019 18:25
@Rich_Laue good idea, blame Android and walk away.
BTW, in my initial post, I told you how I'm able to get it working, and how to recreate the issue. I didn't have to reboot the watch or the phone. It's reproduceable.
I think the proper approach for a product advocate would be to qualify the bug, get more information, look at log files, work with developers and own the issue. But to each his own.
01-05-2019 19:49 - edited 01-05-2019 19:57
01-05-2019 19:49 - edited 01-05-2019 19:57
In what way am I blaming Android, you still haven't even mentioned what operating system your phone uses.
As a fellow Fitbit user, with no other relationship with Fitbit, or the development team. What is it that you are asking me to do, considering that you have as much a pull with Fitbit as I do.
As for Android the biggest problem is that there is no consistency with the hardware and not much more with the OS.
With manufactures being able to use their choice of hardware and some heavily customize the OS simply means that one Android phone will work with no problems and another Android phone may need a rewrite of the drivers.
01-05-2019 20:39 - edited 01-05-2019 20:41
01-05-2019 20:39 - edited 01-05-2019 20:41
@Rich_Laue well, thanks for adding pretend value to this thread, now go ride your unicycle to another thread, I'm sure another user will find your rebooting and restarting suggestions useful.
02-05-2020 03:46
02-05-2020 03:46
I also get this exact same issue
I had to force restart my ionic to get the notifications working again
This issue seems to have appeared after the recent firmware updates
Other things that I noticed:
I had notifications re-appear after I had right-swiped them away, even after multiple re-entries + right-swipes
After "Clear all", I had cases of a notification that persisted the next time you came back in to the notification section.
I also see both of these issues