"Do not Disturb" error notification - RESOLVED w/ 2.70

[AlessFitbit]

Fitbit Update 04/19/2018:  Hi everyone - Thanks so much for patiently waiting while we released a fix. I'm happy to report we started rolling out Fitbit for Android version 2.70 yesterday, on 4/18. Each new app version is slowly released, so if you don't see it available in the Google Play store yet, it will be there shortly. This app version contains the fix, so please update! 

If you continue to see the "Do not Disturb" error message after updating, please let me know. I would like to receive confirmation from you all that this app version really did fix it.

Thanks for all your help! 

---

Hi, Android users!

Thanks for reporting this Do not Disturb Error notification with the Fitbit app. We have escalated this to our team for investigation. If I need more information from you all, I'll make sure to ask and update this thread. Thanks for your help! 

[Ckp1017]

Samsung galaxy s9 plus and I am having the same issues as everyone else and my phone is not on dnd........  I have checked all the settings, reloaded the app, reloaded the versa 3 times.....etc.  please let me know.  Thanks

[lisagettinfit]

It’s been fixed?? Then what do I need to do to get notifications because
I’m still not getting them - even with the Do Not DIsturb override.

[LostScientist42]

Here to log another Android app error.

Samsung Edge 7. Please fix.

[Carashere]

Same problem here. If they don't fix this soon, I am going to be buying some other brand of smart watch. The ability to receive call and text notifications while my phone is on silent is the highest priority feature of this device for me.

[SunsetRunner]

Hi Alvaro, I've got a Samsung Galaxy S6 running on Android 7.0 and I'm having the same issue.

[Braddersem]

I'm in the same boat

[RobertoME]

Hi Android fellows and welcome aboard @Stepsup, @Agandhi7, @Luna_rose and @gocabby. As I mentioned before there are no news yet, our team is investigating the root of this issue and I haven't heard any updates since yesterday. Just make sure to keep your Fitbit app updated as the fix will be released in a future version of the app.

In the meantime, as some members has mentioned, a good practice to circumvent this error is adding an exception from your phone settings.

In order to do this you need to access your phone settings > Select Notifications > Look for the Fitbit app > Select Set as Priority (This option may be called depending of the brand or version of Android).

Thank you again for your great patience while we work to resolve this.

[Ctyldsley]

---

@RobertoME wrote:

Hi Android fellows and welcome aboard @Stepsup, @Agandhi7, @Luna_rose and @gocabby. As I mentioned before there are no news yet, our team is investigating the root of this issue and I haven't heard any updates since yesterday. Just make sure to keep your Fitbit app updated as the fix will be released in a future version of the app.

In the meantime, as some members has mentioned, a good practice to circumvent this error is adding an exception from your phone settings.

In order to do this you need to access your phone settings > Select Notifications > Look for the Fitbit app > Select Set as Priority (This option may be called depending of the brand or version of Android).

Thank you again for your great patience while we work to resolve this.

---

This option doesn't exist for me on the OnePlus 5 running Android 8.1.0. My new Versa is pretty much a useless paperweight with notifications not functioning in silent mode.

[EllePrimeau]

My phone is a Samsung galaxy s6 currently running on Android 7.0 software, using a Charge 2. My phone is most definitely not in DND, I have uninstalled and reinstalled the app, tried toggling the DND on and off, turned on all the permissions for Fitbit app, allowed my msgs and calls to be seen on the lock screen and still get this msg in my notifications screen inside the fitbit app. Please help, I really want my notifications back on my Charge 2.

[NexusFitness]

Fitbit are aleready aware of the issue and it will be fixed in the next
update or the one after that again.

[MarreFitbit]

Hi everyone! I'm sorry for the inconveniences this has been caused to you guys. As it has been mentioned here, our team is investigating the root of this issue. As a recommendation, please make sure to keep your Fitbit app updated, as you know, the fix will be released in the next Fitbit app version for Android users. As of today, the version is still on 2.69, so as soon as you see that there's a later version don't hesitate to go for it. 

In the meantime, as some members has mentioned, a good practice to circumvent this error is adding an exception from your phone settings.

In order to do this you need to access to your phone settings > Select Notifications > Look for the Fitbit app > Select "Set as Priority".

Also, I just wanted to let you guys know, that for the ones running non-compatible devices (such the S9+ or the Huawe Mate 10), we cannot guarantee that the next Fitbit app update will fix the issue as we are still testing on these phone models. The developer team is aware of the need to add new devices to the list of compatible devices. 

Thanks a lot for your patience and understanding with this matter. Let me know me if there's anything else I can do for you in the meantime. 

[NexusFitness]

Please do add the Sony Xperia z5 in compatible devices. 

[MarreFitbit]

Thanks for stopping by @NexusFitness!  There are some users who can synchronize with non-compatible devices. If your phone meets the requirement of Minimum Supported OS (Android 4.4 KitKat), you can try the tips on the following help article: Synchronization troubleshoot or even notifications troubleshoot. 

But please don't forget what I just said above. If the tracker gets to sync, we don't guarantee that the functionality will be optimum as we are still testing on this phone model. Our Android team has not added it to the list what means that we don't have a estimated date on when it will be added, but we are aware of the need to add new devices to the list of compatible devices.

I'd recommend checking out our Feature Suggestion Board if you haven't already. This is a space where Community users can post features, ideas, and suggestions that they'd like to see in future Fitbit products, accessories, and software and top-voted suggestions get relayed to our product team for review.

I'd also recommend up-voting and commenting on Sony Xperia Z5 Compact Compatibility  feature suggestion since it is very similar of what you're looking and asking for.

Have a great day! 

[DAtkinson86]

My Fitbit HR is saying my do not Disturb option is on when it's clearly not according to my phone settings. Any suggestions?! I have screenshots but am not sure how to upload to here.

[Amyjane1988]

Mine has done this over the last few days. I receive notification for whatsapp but not calls. I'm on the charge 2 and on Samsung S7

[SunsetRunner]

I have a Samsung S7 and on silent it says Do not disturb on fitbit app. If I have my ringer on, error message goes away. Defeats the purpose!

Please fix!! With all these issues, considering returning my Versa

[noahalan]

I'm having the same issue with Galaxy s8

[noahalan]

Galaxy s8 running Android 8

[Mbkelly26]

Same issue for me. Samsung galaxy S6,  Android 7.0, fitbit firmware 22.22.55.2. Other poster is correct, putting ringer in silent does seem to be perceived as do not disturb by fitbit, which was not the case previously. 

Work around until fitbit resolves the issue - set your phone to vibrate and then turn your vibration intensity all the way down.  Its basically the same as silent mode in practice, but looks it like vibrate to the fitbit app. 

[Caza73]

I'm having the same issue with my Samsung Galaxy A5 2017. I only bought my fitbit last night, and this was one of the features I wanted. If not fixed soon I will be returning for a refund!