RESOLVED 06/16/2018: "Notification service not running" error

[AlessFitbit]

Fitbit Update 06/16/2018

Thank you for reporting the error is not longer showing in the Fitbit app. This issue has been resolved with the release of the Fitbit app for Android, version 2.73. If you're still experiencing issues receiving notifications. Make sure to confirming that you're updated to the latest app release and following our notifications troubleshooting tips provided in this help article.

I'm moving forward in closing this thread as the issue has been resolved and there is no need to post future updates. If you have questions regarding the Compatibility of your phone, refer to this help article: Which phones and tablets can I use with my Fitbit watch or tracker?

Thank you for your continued patience as we worked to get this resolved.

_________________________________________________________________________________

Fitbit Update 05/09/2018

Hi, Android users!

Some of you may be seeing the following error message inside of the Fitbit for Android app:"Notification service not running. A phone restart is required to re-enable notifications on your tracker." Even if you perform a restart, the error message persists. 

Thanks for reporting! Our team has been notified and are investigating. We will make sure to update you all if we receive more information. In the meantime, we appreciate your patience. 

[SilviaFitbit]

Hey everyone!

I'm glad to see that after the app update the notifications are working for most of the users. You can make sure your phone is compatible by checking the list of supported devices here. If you have a compatible device but it's still not working please unpaired from Bluetooth, restart your phone and follow the set up notifications again. 

Hey @Wilkind1, thanks for sharing the steps that worked for you. 

Hope this helps! 

[Bamox]

I don't think the FB Moderator has the foggiest clue what they are talking about. My ASUS phone (and hundreds of other brands/models) is not listed as "compatible", but had no issues receiving notifications on my Blaze tracker for the last 17 months. Why is it so difficult for FB to admit that we screwed up something and are working to fix it? So frustrating. 

[PaulHaines]

Exactly the same issue here.  I also have an Asus Zenfone.  Notifications worked fine when I first had my Ionic.  Then stopped working and no matter what I tried it would not come back.  A total factory reset and rebuild from ground zero and it started working again.   But only for 2 days.  Now..... zero notifications and that STUPID MESSAGE in the app

[Another-problem]

Just received the new update 2.69 and it's now all working fine. Guessing fitbit fixed their bug. Would have been nice to get a "Sorry about the problems, but should be fine now" message. Odd thing is that I'd unpaired the fitbit from my phone so it seems to have paired itself!

Get Outlook for Android

[PaulHaines]

Wish it was as simple as that. I had upgraded to 2.69 too and like others
have reported, it didn't fix.
However, a total uninstall, un-pair, reboot both phone and device, and then
reinstall the app. When you navigate to the notifications settings in the
app, it then asks you to authorise the apps permissions to the notification
service in android
On doing all, yes all, of this, my notifications came back
Who knows how many days for though

Fitbit really must tell people what the root cause is, and the workaround
until they fix it properly.
This not being in device compatibility list is a total BS weak response. If
that is their response in post sales, they should use the same messaging
during presales, with a published list on every stand or every online store
page and big warning "This device may not work as advertised if your phone
is not in this list"
And let's see how their sales do then.

Cmon Fitbit, sort this issue out, regardless of which physical android
phone

[Wilkind1]

I've noticed that I seem to have the issue when the app is on the SD card. However when it's on the phone memory it seems OK.  Let's see how long it lasts

[AnnetteH]

HI, getting the same message, really annoying. Phone call notifications are coming through but not texts or calendar. Simple question to FitBit "How do I fix it" I have tried blue tooth on, blue tooth off, notifications on, notifications off, device on, device off. Everything the instructions tell you.

Help, have wasted an hour this morning trying all the options. people are referring to an OS upgrade, is that the phone, app or both and how do we do this.

Moderator Edit: Format

[Cutie_pie]

I tried restarting, reinstalling, nothing worked too.

eventually tried “Fitbit notifications” by Smart Dinosaurs Entertainment.. and I have notifications 

[AnnetteH]

OK. I have gone into play store on my phone (Samsung), found fit bit app, it offered an update to 2.69. updated. rebooted phone, checked all were talking to each other via blue tooth. test call - notification received, test calendar entry - notification received. test text message - notification received. So on my Samsung S5 Neo Android the upgrade to 2.69 has worked and notifications are now working. Would it not be useful if FitBit had a selection of phones to test new apps on, before release, or run more complete testing and not get the community to actually do their testing for them..

Thanks to all for suggestions. 

Moderator Edit: Format

[theresa71]

I just downloaded this app, the test notification worked.  Why cant Fitbit do this, instead of having a separate app?  Thanks for the info.

Update:  I uninstalled Fitbit notifications by Smart Dinosaurs Entertainment.  (I think I kept accidentally closing the app preventing it to work).I eventually uninstalled the fit bit app and re-installed it.  My text notifications are now working.  Someone else mentioned that it works if the app is saved to device storage and not the SD card storage.  My app is currently saved to my device storage (previously was on SD card storage). I am leaving it there and not testing the SD card storage.  Hopefully notifications will continue to work.

[Bamox]

 Switched to Bluetooth Classic and problem is fixed at least for now. But it drains both batteries at a supersonic speed. So, the problem is not satisfactorily solved.

[PaulHaines]

Well after installing 2.69 and total reinstall, I had notifications working
for 1 day.
Now back to that stupid message and no notifications

This really is crappy unstable software

Fitbit please resolve this

Regards,
Paul

[KiwiDalang]

I'm using a Meizu Note. It was working, and following your modifications now is not working. Should I now go and seek a refund from the seller as it's no longer fit for purpose?

[KiwiDalang]

Ditto on having it since it first came out. It was a bit wobbly for the first few days, but now is completely broken. The SW isn't getting better; it's getting worse.

[KiwiDalang]

Does. Not. Work. They have introduced a SW problem. They need to fix it.

[SunsetRunner]

---

@Wilkind1 wrote:

I've noticed that I seem to have the issue when the app is on the SD card. However when it's on the phone memory it seems OK.  Let's see how long it lasts

---

I found the exact same thing.  I moved the app off my SD card and the notifications are working again, no issue.  Thanks @Wilkind1

[RobertoME]

Hello everyone, thank you for your feedback and for bringing this issue to our attention. Also thanks for sharing your workarounds to address this issue.

As you are aware, it was released a new version of the Fitbit app that address some issue in the stability of the app. My recommendation is to install this new version in case you haven't done so and once is installed proceed to reset the app:

Log out from your Fitbit app and go to your phone settings. Access to the App manager option and look for the Fitbit app in your downloaded apps list. Once you are there, clear the app cache and data and proceed to "Force Stop" the app. Finish the workaround by restarting your phone. When your phone has initialized, go back to your app and try again.

Something that is true, is if the app is not installed in the internal storage of the phone it may present some delays or malfunctioning based on previous user experiences. So the best is to maintain the app installed in the internal storage.

Also, a quick note worth to mention is that if the phone is not listed as compatible, it may present some odd behaviors due to the app is not optimized to work with the device in question. This doesn't necessarily mean it won't work, is just we cannot guarantee the behavior will be the expected one. For more details please refer to this article: Which phones and tablets can I use with my Fitbit watch or tracker?

See you until the next opportunity.

[Bamox]

Really, Roberto?

[PaulHaines]

Hi Robert

Actually after uninstalling 2.68, unpairing, rebooting phone and device, installing 2.69 and logging in, when selecting notifications it asks you to grant permissions for notifications.  

On doing this, notification services returned.

BUT - less than 1 day later it all stopped working again.

Others that have upgraded to 2.69 have similarly reported that it has not cured the problem.

I got it working again but going through the whole unistall, cleanup, reinstall process over again - clearly this is not a workable solution.  I have had 2 days of working notifications though.

Is it related to phone being disconnected from the device over Bluetooth for a considerable period?

On the compatible device comments - of course we all understand you have to state that, providing a  defence.  The reality though is that there are so many models of Android, and I am sure you don't want to limit sales to only owners of phones on the compatibility list, your revenues would tank.

So the best thing is to keep this issue in the face of the development team for fixing, and communicate to Fitbit owners the root cause and easiest workaround as you work a proper solution

Many thanks,

[octupuslau]

---

@SunsetRunner wrote:

---

@Wilkind1 wrote:

I've noticed that I seem to have the issue when the app is on the SD card. However when it's on the phone memory it seems OK.  Let's see how long it lasts

---

I found the exact same thing.  I moved the app off my SD card and the notifications are working again, no issue.  Thanks @Wilkind1

---

After installing Fitbit app 2.69 on my Samaung S9+, notification works fine. Then it didn't work again and I didn't know why. I then tried to move the fitbit app data back to the phone. It worked again and so far so good. I hope this could solve some of other users' notification problem and at least it works for me.

Steve