07-02-2019
08:55
- last edited on
07-14-2019
17:22
by
LizzyFitbit
07-02-2019
08:55
- last edited on
07-14-2019
17:22
by
LizzyFitbit
Interesting that the Fitbit 3.0 version that came out on June 27th has a pretty serious bug in it that stops txt notifications to fitbits (Blaze) from numerous phones. I have tested with 3 different Blaze trackers and Samsung S8, S9 and S10 phones as well as LG G5s.
On 2.95 txt notifications work fine. Update the app to version 3.0 and notifications stop. Yet you can successfully test a phone call and receive incoming call alerts just fine. Rebooting phone and tracker, no effect. Turning notifications on and off, nothing. Clearing data and cache of app, nothing. All permissions are correct. Deleting bluetooth pairing, rebooting tracker and phone, nothing.
Uninstalling 3.0 and going back to 2.95, everything works just fine on all phones mentioned. Txt notifications included.
I am disappointed that Fitbit claims it is the device when it is clearly their poorly written software that caused the issue. Let me know if you want to know how to roll back to 2.95 to fix your notifications. ****This is at your own risk*****
Moderator edit: updated subject for clarity
07-02-2019 22:49
07-02-2019 22:49
Hey, i was having issues as well with the 3.0 update, no text messages were coming through. I rolles back to version 2.95 and still having issues with the text messages. Any ideas?
07-03-2019 04:37
07-03-2019 04:37
What type of phone? What type of tracker? Is everything but the txt working? Do you get call notifications?
07-03-2019 06:23
07-03-2019 06:23
07-03-2019 08:10
07-03-2019 08:10
Okay, on your phone. Go into the Fitbit app, go to help and verify the version and build number of the app for me please.
07-03-2019 17:32
07-03-2019 17:32
07-03-2019 17:56
07-03-2019 17:56
Okay good. Have you restarted both the fitbit and your phone? Are all the app permissions set and is the text messaging application for the fitbit?
07-03-2019 18:09
07-03-2019 18:09
07-03-2019 18:11
07-03-2019 18:11
Does the test call notification work?
07-03-2019 18:20
07-03-2019 18:20
07-03-2019 18:46
07-03-2019 18:46
What about the Fitbit app permissions in Android? How are they set?
07-03-2019 18:51
07-03-2019 18:51
07-03-2019 18:58
07-03-2019 18:58
I am at a loss as to what is different with yours. I have an S8 with a Blaze that is working just fine.
What carrier is your phone? Do you recall when it stopped working? last week-ish?
When you downgraded, you uninstalled the old version?
07-03-2019 19:00
07-03-2019 19:00
07-03-2019 19:03
07-03-2019 19:03
Okay, so you are out of the US?
Try this then. Go back 1 more version. Something prior to 2.95.
07-14-2019 17:21
07-14-2019 17:21
Hi @jreiter2019 and @Xxhemipowerxx, welcome back. I'm glad to see you here. I'm sorry for my delayed response.
Fitbit releases updates for the Fitbit app and works together with the functionality of the Android version so both can work together. For this reason, we don't recommend to use an old Fitbit app version as we don't guarantee that it'll always work to sync or receive notifications.
@jreiter2019, thanks for taking the time to share your feedback, as well for the steps that you've tried so far to get your device working again. I understand how you're feeling, our team keeps working on each device, and your comments are a great help to implement improvements. I appreciate you for helping other friends in this thread. If you have any other question, feel free to let me know.
@Xxhemipowerxx, thanks for letting me know about your Charge 3. You've done a great job with the troubleshooting steps! I've confirmed that your Samsung Galaxy S8 is a fully supported devices, and to further investigate, may I know the Android version of your phone? Although you've tried troubleshooting your device, I'd recommend to try the following:
I look forward to your reply.
07-26-2019 12:01
07-26-2019 12:01
Same issue with Pixel 3. Phone calls go to Blaze but not messages. Started recently. Have tried both Bluetooth and Bluetooth Classic settings on the Blaze. Had phone "forget" both past Bluetooth profiles. Restarted both multiple times in different sequences.Turned off Notifications for a while then back on.
Even disabled Text Messages in the notifications section but enabled notifications for the specific SMS app I'm using, which is Google's Messages.
All-Day Sync and Always Connected are both enabled.
Blaze current version shows 17.8.402.1
App version on phone is 3.2 (20213412)
Not a happy customer. Also had to replace my wife's Charge 2 for the screen cracking issue so many have experienced.
How do you roll back to an earlier version to troubleshoot?
08-02-2019 12:31
08-02-2019 12:31
Hi @tocsik87, welcome to the Community. I'm sorry for my delayed response.
Thanks for the information provided, as well for the steps that you've tried prior posting. I'm sorry that you had this experience with your wife's Charge 2, and your Blaze. Currently there isn't an option to revert the Fitbit app version, but I'll help you out with this situation. Since your Pixel 3 phone is a supported device, I'd recommend to give a try to the following steps:
Let me know how it goes.
08-04-2019 06:38
08-04-2019 06:38
Thanks for the information. I started the process but stopped short of setting up my Blaze as a new device. Wanted to hold off and ask for clarification. All other functions and communication between my Blaze and Pixel 3 are working as expected except for SMS notifications. Same issue reported by so many users.
If I setup my Blaze as a new device will I lose all my historical data that is still working? In particular, steps, exercise, sleep etc.?
It just seems there is no issue with connectivity and call notifications etc. Just text messages. I will try setting up as a new device if historical data is retained.
My Fitbit tracks data that provides a discount on health benefit costs through my employer upon reaching milestones, so this has a direct financial impact for me.
08-06-2019 20:12
08-06-2019 20:12
I've got the same issue ^ blaze and pixel 3. Was thinking about getting a new watch maybe its time to look at something besides fitbit.