Fitbit WON'T fix Blaze notification issues!!

[thenameless1]

I'm hoping to grab the attention of some of these moderators. At the very least i'm sure one will chime in welcoming me to the community as this is my very first post!

I figured i'd at least present some facts as this was an issue Fitbit new prior to the release of iOS 13 and chose to do nothing about. It be safe to assume that everyone has opened their Fitbit app recently and saw the popup message for for $50 off the versa 2,  but does anybody remember seeing a popup message saying, "Hey we are having issues with notifications in iOS 13. If this is an important feature you may want to hold off updating until we resolve the issue" 

Some supporting facts:

1. iOS 13 was released on September 19, 2019.  On or around June 3, 2019 Apple released the beta for iOS 13 so all the app developers could check their apps compatibility with the update. Fitbit had 3 months to address the notification issue PRIOR to the release date. It seems as though Fitbit opted to do nothing about it. They also had the opportunity to warn users, which they opted not to do either.

2. Since the release of iOS 13 Fitbit has updated there app 5 times! I referenced this portion of the website https://help.fitbit.com/articles/en_US/Help_article/2025 Fitbit updated the app 5 times in 2 months and they still can't fix the issue?

Anyone else think its a little odd that we are seeing ads for $50 off the versa 2 instead of updates on the notification issue?

My issue is that based off the information accessed today on the Fitbit website like product descriptions and the phone compatibility checker all say that i should have notifications on my blaze which i don't.  Calling customer service doesn't help and i'm not sure what a 25% discount on a new fitbit really does. Fitbit broke my blaze and the fix they have is to go buy a different one?  I'm not sure why it should cost me or anyone else experiencing these issues money for an issue that Fitbit has chosen not to address.

Since this product is technically not supported by Fitbit anymore information on their website should be reflected to show that as of ios 13 the blaze will no longer receive notifications. Otherwise, Fitbit should should start issuing 25% cash back off the last retail price for the blaze instead of 25% discount on a new Fitbit.

I'm sure if Fitbit was offering cash back we would all have a fix for the issue immediately!

Realistically though they had 5 months to fix it and if they couldn't do it by now they aren't going to.

[Odyssey13]

Hello and welcome to the forums @thenameless1  just a thought on this: "Anyone else think its a little odd that we are seeing ads for $50 off the versa 2 instead of updates on the notification issue?"

I don't see anything odd about it. When you go to a car dealership, the sales people are selling you a car and not talking to you about the process involved in getting the car serviced. It's completely different areas. The mechanic can't speak about the current sale prices and the sales person has no idea the procedure to get the front end aligned.

Sorry you're having problems. I'm sure you'll get a response from a moderator.

[thenameless1]

I'm kind of new to the forums and i'm not sure how this post got moved to the ios section or why.  Maybe one of the moderators can put it back where it was originally posted so i don't have to double post.

@Odyssey13 I appreciated you chiming in, but it is kind of odd.  Fitbit has the ability to provide ads on their platform, but they can't provide an update on the notification issue? Maybe i could have worded it better like why aren't we seeing updates on the notification issue in addition to the ads we are seeing? It seems fitbit is more interested in trying to sell a new tracker as opposed to fixing whats currently out there.

I don't quite understand why a scenario with cars was provided, but i wouldn't compare it to a car getting serviced.  Its more similar to the issue that VW was in with its diesel cars. People bought them expecting one thing and then down the road it turned out to not be true.

All i want is my fitbit to work as the manufacturer intended it to. How they currently describe it should work on the website. I don't want to buy a new one because they are choosing not to fix the issue.

3 months before iOS 13 release to fix.  We are currently 2 months after the update  and 5 fitbit app updates in and still no fix? Still no update?  Are they not fixing on purpose to see how many Blaze owners will convert to a new fitbit during the holidays? During this 5 month period there has been no update to Blaze documents regarding  the discontinuation of notifications. Does this mean that in another month or two (which puts us after the holiday season) we will magically have them fixed in an update?

[JuanFitbit]

Hi @Odyssey13 , nice to see you back! Thank you for your comment and information! 

@thenameless1 , a warm welcome to the Community! Thank you for your posts! This one was moved to the iOS board, as your situation, according to our description, is about the iOS app and not about the Blaze! I noticed that you posted your inquiry in different boards and thread. I just want to remind you to the Community Guidelines . 

Regarding your posts and feedback! The offer of the 50USD off on the Versa 2 doesn't have anything to do with the situation with the notifications. This offer is because of the Black Friday season! There is no relationship between the 2 topics. 

I appreciate that you already contacted Support. I'm sure that our Team offered you the best help possible! 

I noticed that you already asked for support on this other thread. Many users have solved the situation and have shared their solution. I recommend you to have a look at older posts there and check the solutions the other Community members have shared! 

I also suggest you to follow that thread as it is being updated with different solutions. 

[thenameless1]

@JuanFitbit  @Odyssey13 

I'm not really sure everyone has found a fix for the problem. And as many have pointed out Fibit has yet to actually post them as an actual fix.  I would like to reference this thread https://community.fitbit.com/t5/iOS-App/Stopped-seeing-notifications-after-updating-to-iOS-13/m-p/37...  Due to the volume of posts and views you can see it isn't resolved.

My issue is with the fitbit Blaze not the actual app. However, now i'm under the impression that whoever opted to move it from the blaze forum to the ios app section is actually acknowledging that the the Fitbit app actually "bricked" the notifications feature in several of their trackers intentionally.  After all Fitbit had time to to work with the iOS 13 beta and opted not to make the necessary compatibility changes to ensure their trackers would work in advance.

I do like how everyone is focusing in on that $50 dollar comment.  The point is if Fitbit has the ability to advertise the Black Friday specials you could have also sent out a similar popup warning users about upgrading?  So why is it that i am able to get a Black friday Special, but not an update on whats going on with the notifications. Surely, it wouldn't have be too hard for @KateFitbit and her team to provide users with an advanced warning.

I'm curious because with Fitbit representatives opting to move this to the ios section its proving to be an issue with the platform as opposed to an issue with my actual device. I have to be honest I'm glad to hear that because the blaze is no longer supported by you guys. 

Now i have to ask. Since its an app issue  why isn't @katefitbit and her team just rolling back to a previous version of the app?

[JoeWeis]

Still having the same issues described here - glad I’m not alone. Like many other Blaze / iPhone owners, I turned to researching proposed “solutions” on the Fitbit community pages - which mainly involved resetting the Blaze device, reconnecting the Bluetooth connection, rechecking the notification settings within the Fitbit app, etc. I have tried all these and nothing has worked. I’m so used to wearing my Blaze that sadly I still wear it despite it’s annoying issues. Prior to iOS 13 it worked perfectly. However, my patience has worn thin. I’ve owned several different Fitbit products over the years - just wasn’t ready to give up on this one yet, so no need for a coupon offer. With the recent acquisition by Google, it sounds like I either need to switch phones or switch smart watches. Time to finally take the Apple Watch plunge? Oh and this is my first post ever on here too. 

[Hankib]

Super annoyed also - can’t get my notifications to work on blaze any longer.  I’ve tried all the Fitbit suggestions and it sometimes gets it to work for a bit and then goes away.  Very poorly done by Fitbit - ignoring the real issue!