Not receiving text notifications

[TopherWar]

I've had this Blaze for a while now. I've had issues before where I stopped receiving notifications and I've always been able to fix it with the tips I've found in this forum. I've tried them all multiple times.

This morning when I woke up and opened the app, there was a notification informing me there was a new Dashboard coming and I could use it if I wanted or stick with the original for now. I chose to stick with the original. Does this matter in any way? I'm not sure, all I know is it's the only thing that I've done different since yesterday and suddenly I'm not receiving text messages. I've re-synced, re-started, set up a new account, re-connected to my phone again, restarted everything again. Nothing works.

I've opened up help chats and once they here all this they start talking about warranty options. I bought this second hand, I don't have a warranty.

So is this is? Am I stuck with a watch that does one less thing now? Anyone else at all having this problem?

Moderator edit: updated subject for clarity

[SunsetRunner]

Thanks!! I ended up finding an app to download and went back tot he 2.95. Works awesome now!! Now if only they can fix the actual problem

[av8r75]

---

@AlejandraFitbit I don't believe this response addresses the problems users are having. Reading the posts in this thread it is mostly experienced Blaze users who have clearly stated that they have tried the standard troubleshooting you linked to. Also it is evident that the problems began in the second week of July across a variety of devices with the push update from 2.9.5 to 3.x.x. Finally there is a known solution but board rules will not allow us to provide detailed instructions for those who are less tech savvy, leaving those users without a core functionality of their device and no indication from Fitbit that the problem is even truly recognized, let alone that a fix is in the works. As far as I can tell the only "solution" offered by Fitbit has been a 25% discount to put towards replacing a device that worked perfectly until a software problem created by Fitbit was pushed across to users.

---

[Dubesor]

You nailed it. I will not buy another Fitbit, because if the way they have
treated Blaze users. I will either go with an iwatch or something by Samsung

[nunzi]

I'm thinking all our phones are compatible considering everything was
working fine until the upgrade.

[kimw19]

Hi AlejandraFitbit,

I don't mean to be disrespectful but please do not jump onto my post and give us all the same rubbish time wasting tips that we may find useful. NO ONE from fitbit is understanding that these issues are not new they are ongoing !!!... month after month.... our Fitbits were brought for a purpose and when something works and then doesn't it is a waste of money !..., it is a waste of my time contacting Fitbit continuously.....IF YOU TAKE NOTICE OF WHAT PEOPLE ARE WRITING WE ARE ALLLLLL SAYING THE SAME THING... THE FITBIT WAS WORKING AND NOW IT ISNT !... do not insult our intelligence by suggesting it is something we are not doing right !... absolutely furious !!!...

[Dollyg112]

👏👏👏

Seriously

[Mdalke]

I am still having this issue too.  I can get e-mail, phone and FB messenger notifications, but not text messages.  I was told by Fitbit that it was my watch and that the update sent last week fixed the issue.  Obviously it didn't if all these Blaze owners are still having issues! 

[Mdalke]

@AlejandraFitbit All the checks and balances have been done on my blaze and my phone.  My phone is compatible.  Even after all of this, I am still not receiving text messages and I see that other Blaze users are having the same issue.  Through chats with support, I have been told that my blaze is defective, yet others are still having the same issue.  When will FitBit correct this?  The latest update didn't fix it.

[Jessica_B_]

This is what I got from Fitbit when I sent them a message on Twitter: "We
appreciate your efforts trying some fix prior to contacting us. With this,
Samsung Note 8 is not yet listed as Fitbit's supported device. Our team is
testing most of the available devices and cooperating with the makers of
this mobile devices for compatibility. We appreciate you for bringing this
up and our team is working to make sure this is addressed. Mind sharing us
the email address linked to your Fitbit account so that we can take a
closer look? Also, may we confirm if you already visit this page to double
check the notification settings: (link:
https://help.fitbit.com/articles/en_US/Help_article/1979/#setup)
help.fitbit.com/articles/en_US…? We'll be waiting and let us know if you
have any questions, we'll be happy to assist."..............I thought it
was working for note 8 before the update though?

[SunsetRunner]

@Mdalke I don't have a lot of faith that this issue will be fixed. It has been going on for right at a month now. The blaze is an end-of-life product. I'm not saying that they created the issue on purpose but I don't think they have a lot of incentive to correct it either. As someone who works in the electronics industry, I know it shouldn't be too tough to see what changed between v2.95 and 3.0 in the app to cause it.

@Jessica_B_ It probably was working before and you have updated the app beyond version 2.95. If you read through most of the previous posts (I know there are a lot with multiple pages worth) you will see that everyone who has moved back to version 2.9 or 2.95 of the app, their Blaze starts working perfectly fine again. You can't get that version of the app from the Fitbit website (at least not that I can find) and we can't post a direct link to where you can get it because Fitbit won't allow it, but I'd be willing to bet that if you follow the directions that have been listed, it will start working again for you.

[themom1964]

I contacted Fitbit and was told my Galaxy Note 8 is not "fully compatible".  However until recently...it was, and on the website it lists this function as something that is.  Like everyone else, I am considering changing trackers if this is not fixed completely soon.

Too bad.  I've been completely satisfied to this point.

[Spanyell]

I also ran into this problem. So they're not going to fix it for real? They can't find some intern to patch the code real quick?

[SunsetRunner]

Just to be very clear, I am not associated with Fitbit in any way at all. This is just my personal opinion, but no I don't think they will fix it. I hope I am wrong!

[Garbutt]

hi is yours working yet mine isnt and its doing my nut in lol 

[SunsetRunner]

Mine is working, only because I uninstalled the fitbit app, downloaded the 2.95 version and turned off my automatic updates

[DivaNancy]

Good morning,

This is not just an Android issue.  This is an iPhone issue, also.  I have the classic Blaze, & I am not receiving any notifications.  I am only able to control my music.  

[Garbutt]

Hi I've tried looking for the other app I cant find it could you screenshot me it please thanks

Sent from my Samsung Galaxy smartphone.

[SunsetRunner]

I got mine from the purple one.....as soon as it downloads, go into the settings and turn off automatic updates

[Garbutt]

Hi I dont know what you mean by purple one lol


Sent from my Samsung Galaxy smartphone.

[Jarlaxel]

Fitbit this is an obvious software problem on your end.  By giving your users and customers the run around and insulting their intelligence by acting like it is something on their phone causing the issue is just plain bad form.  When rolling back to a previous version solves the issue and makes it fully functional again.  This whole issue is starting to sound like the BS Apple does to get people to upgrade a perfectly functional device by modifying software to make it nonfunctional and slow.  I sure hope this is a genuine mistake and is fixed soon.  Or you will have lost another customer.