07-30-2019
11:42
- last edited on
02-03-2026
04:59
by
MarreFitbit
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
07-30-2019
11:42
- last edited on
02-03-2026
04:59
by
MarreFitbit
Fitbit Update: 9/12/19
Hey all!
We're still investigating and working on a fix for this text notification issue on Android.
In addition to not receiving the correct text notification, we're now aware this is also affecting call notifications. Some of you may only see a previous caller's name and not the person actually calling you at the time you're receiving the notification.
When we have more information for a fix, we'll announce it here in this thread. Please stay tuned for updates!
Fitbit Update: 7/30/19
Hi everyone.
We're aware of these issues with receiving only the sender's name from your text messages. This appears to have started with the Fitbit for Android app version 3.0. If you're experiencing this yourself with your Fitbit device, please know we're working on a fix.
While our team investigates this further, we just ask for your patience. Once I have information for a fix, I'll make an announcement here on this thread.
Want to get more steps? Visit Get Moving in the Health & Wellness Discussion Forum.
Answered! Go to the Best Answer.
@IAmAlsoJohn, I am also a software developer, and we both know a bug this major would not make it through 4 versions of any app, especially considering it was brought to their attention shortly after 3.0 was released. That would (should) have been given whatever the highest priority is within their tracking system. If all notifications were broken, or had Android updated their OS, contributing to this issue, then I could agree, but this is literally a case of seeing what changes were made from 2.XX to 3.0, and rolling them back, or correcting the issue. One version of bug fixes is acceptable, 2, frustrating, but by the third, s**t is getting out of hand, but hey, as long as IOS customers are okay, right?
Agreed. This also ties in to my point about how did this escape their "SQA" (quotes intentional) since the most basic of test plans should have caught this. I guess they probably were like "oh well. We'll deal with that in the next scrum. Plan plan plan...."
For others, I found that after rolling back to 2.95 - it didn't work straight away, but I did get it to work eventually. I had to do a firmware update (though, not sure if that was truly necessary), then re-enable permissions for FitBit (definitely important). Finally, I did a hack that I've found often is necessary to get texts to work, which is to turn on/off bluetooth on my phone, ensure "Always Connected" is on in the FitBit app, and turn on/off Notifcations from my watch (Charge 2). Then, voila - it's as easy as that. *eye roll*
Best AnswerThat may have been the issue. I uninstalled and was able to install the 2.95 version, now just patiently waiting to see it it works! Thank you!
Best AnswerAny progress on a fix for this yet? This has been going on for at least a month and it's incredibly frustrating not being able to read messages from my device. Given the other issues people are having with the latest firmware update and Fitbit's lack of support for it (other than trying to force people to upgrade), I'm losing faith in the company and product. It would be nice to know that we're at least getting close to having a fix.
Community Moderators ensure that conversations are friendly, factual, and on-topic. We're here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
Hi everyone.
Thanks to all for the efforts to resolve the issue, sharing the solutions and helpful tips to help other users. We’re aware of this issue and are working to identify a resolution as quickly as possible. We will not be able to provide you with an estimated time frame for the fix to be applied. I appreciate everyone's feedback, I understand that this can be very frustrating, our team is always working on improving our devices and user experiences, and your comments are always welcome.
I am sorry for any trouble. I appreciate your patience and understanding while we work to improve your experience.
We'll be around if there's anything else we may do to assist you in the meantime.
Was my post helpful? Give it a thumbs up to show your appreciation! Of course, if this was the answer you were looking for, don't forget to make it the Best Answer! Als...
@MarreFitbit Perhaps. while you work to find a permanent solution, Fitbit could provide release 2.95 (ie. place it in the Google Play store) so your customers do not have to go to a third party website to download it. We have done the work for you, proving it fixes the problem.
The responses are repetitive and show no sense of ownership of the problem by you or any other moderator either here or through the twitter support page. As noted, the work has been done for you by all of us. Roll back to 2.95 until you figure it out. That, or make a patch download of it so that we aren't picking up malware from other sites.
Big reason I upgraded from a flex was this issue.
I will be filling out amazon reviews soon regarding the lack of customer service. I hope others feel motivated to do the same.
I have the same problem
Just installed the 3.3.1 update. Short story... still not fixed. Even after uninstalling 2.95 and doing a fresh install, setup, permissions, etc.
Back to 2.95 🙄
Best Answer
Best Answer