This topic is regarding text notifications only. All other notifications work as expected. Apologies for long post.
---------------------------------------
I saw a response, yesterday I think, that stated the notification issue was an Android issue. It really isn't. Other wearables don't have issues with notifications, so... Fitbit, why do you? For those of you who don't work in software... I have worked in software development, including mobile apps, for years. When a new version of an OS comes out, the developers who work with that OS usually are on a beta-release program. That means they get early versions of the software so they can start to work with that platform, to test and ensure they can work out all of the issues that may arise. This ensures compatibility when the latest version of the update arrives on our phones. How do you think your apps all work seamlessly when a major update to your iPhone or Android phones happen? Because developers work their long hours off to code, test, and fix issues. Often that's also why there are updates to an app , sometimes several -- because a new version of the OS comes out.
I purchased my Pixel 3 directly from Google when it first came out, I'm using a Verizon SIM, but nonetheless because it was an unlocked phone, I get almost instant updates. When Google pushes an update out, I get it instantaneously. I don't have to wait for my service provider to decide if and when I'll get it. (Right now I'm on whatever the latest system update Google pushed out this month.)
Android 10 was GA back in September (GA = General Availability).
What this all really means is... Fitbit has had many, many months to work with the Android OS to resolve the issue with text notifications. Months prior to the GA release in early September, in fact. It's now been five months and there has been no progress on the issue. Fitbit has barely acknowledged that there is, in fact an issue (in software parlance, this is called a defect, or a bug).
When I logged the issue with Fitbit Support in September, I had requested the issue be escalated to Development. I'm not sure it was. Since then, I *think* but I cannot guarantee this issue has been escalated. I see varying responses posted with all of the same "script" from support: uninstall the app, reinstall the (current) app, reset your notifications, check your Bluetooth connection, and so on. A few state that the device (certain Samsung devices) are not supported by Fitbit. Note, however, that the majority of devices ARE supported. (Also note how appalled I was when I saw the integration issue banner for iOS displayed, but no acknowledgement for Android. When that banner first started displaying, Fitbit had not acknowledged there was an issue with notifications.) So now, it's time to either state that notifications will never work, remove that statement from the list of capabilities, and admit defeat to your customers. Or actually stop, and apply resources to an issue that has been ongoing for five (5!) months now. Please, Fitbit. Just do something.
Fitbit Device: Alta (refusing to change while this is an issue)
Device: Google Pixel 3
OS: Android 10, Security Patch Level February 5, 2020
Default Messaging App: (Google Default) Messages
Text Notification Workaround: Fit Notifications (Google Play app installed)
Future plans: Waiting for Google to come out with a Google Wear device (until I lose patience)
ETA: All notifications worked fine on the Alta with Android OS 9. The Alta is over a year old and outside warranty period. But it's the integration with the OS that is broken, not any of my devices
Community Moderator Alumni are previous members of the Moderation Team, which ensures conversations are friendly, factual, and on-topic. Moderators are here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
Best Answer
