No problem and you might be right. It takes time for stuff to appear -- updates not rolled out at the same time, people having problems and not reporting, people reporting but not in enough numbers to appear on the radar yet... etc...
Anyhow, I made some progress. As I mentioned before, I was receiving one notification but not others on the calendar. I did some digging and found that the one reminder was set to give a notification and not in text format. I found a drop down list for the type of notification for the reminder to send (text, notification and email). I had all mine with the exception of one set to text. When I went back and set the type to notification for reminders and calendar events, notifications appeared on the FitBit.
Now, I hope the Wunderkind at FitBit are paying attention. The part of the Fitbit App that is broken is the messaging notification. If the type of notification is set to text, it ain't going to happen. Moreover, if notifications are set to a mix of email, text and notification the result is that only some them will get to the FitBit. The hit or miss appearance of the notification symptoms are caused by the mixture of notification types with text.
Finally, I am not a FitBit App expert, but I would guess that the messaging part of the app is trying to read the complete list of messages and crashing or that it crashes when it tries to send a text and does not have permission. In any case, it appears you guys broke your own product with the last update -- I suspect the quick reply feature.
For people trying to trouble shoot the problem. If you can send the test notification from the phone app, then the connection is good. Clearing memory, uninstalling, reinstalling, shutting down the FitBit, factory resets, etc... will not work if the notification type is set to text on the relevant app (Calendar, etc...).
Anyhow good luck... I am going to try something. I will post results...
