07-30-2019 11:42 - edited 01-16-2020 09:35
07-30-2019 11:42 - edited 01-16-2020 09:35
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.
08-13-2019 00:57
08-13-2019 00:57
I too was having an issue with my Fitbit not showing me the message just the person who sent it. I went and googled how to downgrade an app to my specific phone. I had step by step on how to do it. I had instructions on downloading an a p k file in place of the app. Since I did that my Fitbit has been working fine.
08-13-2019 02:05
08-13-2019 02:05
version 3.3 does not work ...
08-13-2019 06:35
08-13-2019 06:35
Where do you find a legitimate version of the 2.95 a p k that won't possibly corrupt your phone?
08-13-2019 06:48
08-13-2019 06:48
You do not have to make an announcement, you have to make it work again
08-13-2019 06:55
08-13-2019 06:55
on A P K M I R R O R, then I pass it to the antivirus. there is always a risk.
08-13-2019 07:11 - edited 08-13-2019 07:11
08-13-2019 07:11 - edited 08-13-2019 07:11
How do I install it? 2.95 that is. I have it.
@dyocma wrote:on A P K M I R R O R, then I pass it to the antivirus. there is always a risk.
08-13-2019 07:29
08-13-2019 07:29
I have it back to 2.95
08-13-2019 08:18
08-13-2019 08:18
Just adding my name to the list of dissatisfied users who are wondering why there have been 3 additional versions of the app released, and still no fix. This seems like a pretty big issue, yet no urgency to correct it. One would think that you could look at what was changed before the release of 3.0 that broke it.
08-13-2019 09:56
08-13-2019 09:56
I rolled back to 2.95 as suggested by a few of you, and I am back in business. Thanks to all who suggested, and I suppose I will stay on this version until they fix the issue.
08-13-2019 10:32
08-13-2019 10:32
For those who rolled back to 2.95, don't forget to turn off auto update for the Fitbit app on Google Play.
08-13-2019 12:15
08-13-2019 12:15
Come on, Fitbit. My patience is over. Where was your SQA before you rolled out this massive bug? How could you miss this when it is easily reproducible, 100% of the time on many, many different Android devices?? Repro steps: Send a text. Fitbit device doesn't show message. It's that simple. Do you have any test plans at all before you push updates?
Secondly, we are approaching 2 months without an officially supported fix. How can this issue be so difficult to debug? Are you guys really trying? Look at the change history, revert offending commit. Not that hard. There is no way that the features introduced (if any? Looks the same to me) in version 3.x outweigh the loss of major functionality. Give users a way to download 2.x in the meantime, at least. Looks like I'm going to have to search this community thread to figure out how to do that - not cool.
Bottom line - I'm tired of hearing "we're working on it". Get an officially supported workaround out now, and meanwhile find some resources to actually, for real, "work on it". If the engineer who is "working on it" is still struggling after 2 months, you need a new person. Your reputation - what is left of it - is on the line. Bugs can happen (although of this magnitude, really shouldn't. I'd be really embarrased if I was FitBit right now) - but don't make us feel like suckers for having bought a device that only works sometimes.
</rant>
08-13-2019 13:27
08-13-2019 13:27
I was told a few days ago during an online chat with Fitbit that my issue with the text messages not showing up on my notifications (just the name of my contact appears) would be resolved once the latest update (22.58.0) was rolled out to me. Lo and behold, I received the update today! However, I'm STILL having the same issue where my notifications on my device only show the name of the person texting and not the actual text message itself. I don't know why this feature stopped working recently, but even with the latest firmware installed today I'm still having the same issue. Any ideas? I'm ready to say goodbye to Fitbit and choose another tracker. Seems Fitbit's answer is to buy a new device, but if they aren't going to stand by their product, I don't think so!
08-13-2019 14:19
08-13-2019 14:19
How do i turn off auto update for fitbit? I have Android phone.
08-13-2019 14:23
08-13-2019 14:23
Open the playstore and go to the Fitbit app. In the top right corner of the screen you see three dots. Tick on those and you can switch automatic updates on and of
Hope this helps
08-13-2019 14:26
08-13-2019 14:26
Done. Thank you!!! Have a great day!!!
08-13-2019 16:20
08-13-2019 16:20
I just downloaded the 2.95 update and working great and turned off auto update. I cant wait for Fitbit to fix it. Ridiculous.
08-13-2019 16:30
08-13-2019 16:30
08-13-2019 16:30 - edited 08-13-2019 19:30
08-13-2019 16:30 - edited 08-13-2019 19:30
Applied the firmware update (22.58.0) for my Charge 2. My expectations weren't very high but updated to app version 3.33 again. Notifications still don't work! Sender only. Rolled back to 2.95 again and surprise, surprise, notifications work.
I'm done with this garbage. I'll stay on 2.95 while I shop for another device. My prediction: this won't get fixed for at least another month. Just like what happened last year for similar issues. It took 3 months for a fix.
My advice: always turn off auto update for the app on Google Play and, once it's finally fixed, wait at least three months before updating to a new version. Or, buy a different device. That's what I'm doing.
This is just downright maddening and unacceptable!
08-13-2019 16:30
08-13-2019 16:30
@Mushugirl wrote:I just downloaded the 2.95 update and working great and turned off auto update. I cant wait for Fitbit to fix it. Ridiculous.
Where did you get 2.95?
08-13-2019 16:31
08-13-2019 16:31
How do you do that? I was told by fitbit support you can't. This needs to be fixed asap!!