No text alerts

[Andrewjames1]

I have a versa 2, and the text message alerts stopped. This coincided precisely with the IOS update on my phone. Everything else works, (FB messages, calls, email, etc) but the texts don’t come through. I have scoured the Internet looking forward a fix. I have deleted and loaded the app a few times, reset the phone and watch several times, forgotten the re-paired the watch., all to no avail. Anyone know how to fix this? 

[Rich_Laue]

Hello @Andrewjames1 since your asking an old question, have you chef the ios board? 

Required settings changed for notifications on iOS... 

[thenameless1]

It's my understanding that android users are having issues with notifications as well. Here is a link for the android issue.  https://community.fitbit.com/t5/Android-App/Notification-issues-after-updating-to-Android-10/m-p/378...

Now android and ios are two totally different operating systems, but since they are both experiencing the same issue it's most most likely the fitbit app causing the issue.

Version 3.xx of the fitbit app has a ton of bugs and is unstable!  As can can be seen here in the fitbit app update history  https://help.fitbit.com/articles/en_US/Help_article/2025/  Fitbit  has made some bug fixes and stability improvements, but it seems as though they haven't quite found the one causing the notification issue in the android and ios apps yet.

[Rich_Laue]

Only those with Android 10 and iOS 10 are having text issues. 

We have instructions on the iOS board for iOS users. And specific help for android users in the Fitbit help. 

Considering that the iOS app is written for iOS, and the android app is written for android. The two are not interchangeable. I doubt RHR common point is the app. 

[thenameless1]

The most current android and ios versions are having issues with the same version of the fitbit app version 3.xx. I don't remember ios having a notification issue with version 2.xx of the fitbit app.  I believe you are an android user.  Were there any issues with notifications with version 2.xx for android?

Software exists that allow you to port an app for android over to ios and vice versa.  Here is one such example  https://stormotion.io/blog/how-to-convert-android-app-to-ios-app-and-vice-versa/.  Fitbit could have used something similar for their app. I'm not saying they did,  but if so the bulk of the apps would be the same and minor differences based on the permissions/api calls between the two app platforms. 

The android app and the ios app are one in the same. I use an iphone i do however keep an android phone in the house for home automation purposes.  I put the android app on android phone. Changes i made to the settings in the android app, changes to the today screen and stuff like that were reflected in the ios app.  I didn't make those changes on the iphone.  So if the android app and the ios app aren't linked in some way how did that happen?

The only common denominator here is the fitbit app! Judging from the fact that the instructions for ios and android users work for some and not others reinforces the fact that the issue lies within the fitbit app.  Fitbit  should roll the app back to the last stable version which would be 2.xx

Now, @Andrewjames1 may benefit from the link you provided, but it doesn't explain why others in that thread still can't get it to work.

The only proper way to fix the issue is to fix the app or as a temporary fix fitbit should roll the app back.  Version 3.xx of the fitbit app shouldn't have been released to the general public with this many bugs and stability issues. Version 3 of the fitbit app was released on 7/2/19.  Its been 7.5 months and there have been no new features released in the app. All they have been doing is fixing bugs in both ios and android apps.

[Rich_Laue]

I have absolutely no issues with the latest or any version of the Fitbit app for the last 11 months. 

However I'm running android 9 not android 10 which is the version that has issues. Then again with every major android version update fit it seems to have issues for a few months. With the latest iOS apple made changes that voucher 3rd parties. Garmin also, these changes have been worked out, then an iOS release added an issue. Many people have stated that when they called the help line, Fitbit was able to talk them through the settings. Some said preview has to be turned on. Others mentioned the DND canot be turned on. 

[thenameless1]

@Rich_Laue I'm pretty sure all the people that are still having issues with notifications on the iphone aren't following them exactly. I know the notification issue with the iphone wasn't fitbit fault, but i do believe they could have handled it a little better.

My issue is the app updates themselves. I don't understand why its so hard to provide users with release notes on what changed with the app. I find it hard to believe that @LizzyFitbit  is all over the forum, but if fitbit can't provide her with an update of whats changed how do they expect her to really help anyone. Even @KateFitbit replied to a thread acknowledging that its something the community wants, but we have been through several updates and nothing has changed.

I hope you don't take any offense, but my goal is to try and promote that change by referencing threads in the community and referencing information provided by fitbit. If all they are are going to say is "bug fixes and stability improvements" and i see something that is working for someone, but not someone else it's going to be because the app is full of bugs and unstable.

Granted in this case with the notification issue it's more than likely that the user didn't follow the directions properly, but none of the moderators are following up with them reinforcing the steps in that thread. So it works for some not other and then an app update with "bug fixes and stability improvements" i have to go with what fitbit provided.

I'm just hoping they see the comments  and start providing actual updates!

[Rich_Laue]

Yes everyone is aware that with the latest iOS version, it is only texts that have an issue. That is what this pinned post is about. 

Please make sure you follow all the instructions in the quick tip section here.

If you still are having issues, please review: 

• Make sure you've updated to iOS 13.3
• Turn OFF and then back ON Share System Notifications (toggle OFF and ON)
• Set Show Previews to Always or When Unlocked

If you still have issues we recommend reviewing the help article. 

As for simply moving the android over to iOS, since Fitbit writes their own Bluetooth drivers this will not be possible. This has required Fitbit to customize the app for specific Android models. BTW I'm not sure why the standard drives can not be used but Garmin does the same. 

[MrMarv]

@Rich_Laue -

But the pinned post and the other informational documents relative to notifications will not help if there is a pairing issue. When that is the case, the most important steps cannot be completed.

No "Information icon" in iOS Bluetooth settings screen:

No access to the device "Notifications screen":

Pressing "Set Up" does not help, no matter how many times you try.

Support states the developer team is aware and are working on it.

It is a pretty well known fact that iOS 13 currently does not "play well with others" when it comes to Bluetooth - Google it.

BTW, the ability to set "All-day sync" is hampered, as well. The same pairing request is displayed.

[Rich_Laue]

Yes @MrMarv that is what we have been saying for a few months. Apple is not playing nice.