Not receiving notifications after Fitbit app update on Motorola Z2 Force

[pizzaboy192]

Phone: Motorola Z2 Force, Android Pie, Fitbit Blaze. I've tried all v3.0 versions of the app available from a mirror and the latest version from Google Play. They all exhibit the same behavior. Every other notification comes in, except those for the Android Messages app.

As soon as I roll back to v2.95 my notifications come in, so I know it's not my phone or it's OS but an issue with the v3 of the app.

I've tried: telling the Fitbit app that a different app is the default messaging app and selecting Messages as another app I want to see, and it doesn't fix it.

Rebooting phone, Fitbit, etc.

Factory resetting the messages app, Fitbit app, etc.Factory resetting my phone.

Nothing but rolling back to v2.95 fixes it.

Moderator edit: Subject for clarity

[RicardoFitbit]

Hello @pizzaboy192 welcome to the Community Forums, your post is appreciated.

Thanks for all the information and details that were shared in your post, my apologies for the inconvenience you're experiencing with the notifications feature on your Fitbit Blaze. Also, thanks for troubleshooting this situation prior bringing it to my attention. Let me share with you that your Motorola Z2 Force is not currently listed as a compatible device with our products and services, reason why you may experience certain connection difficulties with the recent Fitbit app versions.

I'm aware that some users are able to use non-compatible devices with our Fitbit products, however, we cannot ensure a proper function of all its features due to this compatibility concern, Android, Fitbit app and device updates. That being said, even though your mobile device is not compatible, please check: How do I get notifications from my phone on my Fitbit device? to verify if there's a missing requirement that's preventing the notifications to come through. 

Then, please try the troubleshooting steps that are specified on: My Fitbit device isn't receiving notifications from my phone and let me know how it goes. If by any chance you're still unable to receive notifications, I suggest you to try with a compatible device instead and let me know if after trying with a supported device, and the latest Fitbit app, the notifications are received in your Fitbit Blaze.

I'll be here if you need anything else, please keep me posted.

[pizzaboy192]

So it is not compatible because there are known issues or because Fitbit hasn't tested the hardware?

The phone used to work without problem (and still does) with v2.95 of the software so there's an issue with v3.x of the Fitbit app and Android pie.

I can dig out my Moto g5 to test this as well. I've seen reports of the issue via Reddit which is where I found to use v2.95 so I would assume the issue is a bit bigger than a single device.

If I can test and confirm the same issues with a supported device can Fitbit actually look into it? I'm disappointed the response is "won't fix because it's an unsupported handset"

[pizzaboy192]

Alright, to add another two data points:

Had to find phones that were running Pie and used Android Messages as the default messaging app.

Found: Moto g5, and a pixel 2. Both also exhibit the same behavior with my Fitbit blaze. Android Messages does not send notifications but all other apps and notifications come through. It's an issue with v3.0 of the app and Android Messages notifications, not an issue with the phone.

Please keep looking into this. Thanks.

[RicardoFitbit]

Your reply is appreciated @pizzaboy192, sorry for the delay in responding your post.

Your mobile device isn't compatible because we haven't tested the device with our products and services to ensure that everything will work as intended. As per previously mentioned, because of firmware, Fitbit app, Android and device updates we cannot ensure that all your Fitbit features will work as the way they were designed. Please review our list of compatible devices and try with a compatible device.

If after trying with a compatible device you still experience the same situation, please contact me back. I'll be around.

[pizzaboy192]

Hi @RicardoFitbit

First, I've confirmed it also happens on a pixel 2 and a Moto g5, (see above reply)

Second, I ask you to undo the edit you made to my post as it muddies the waters and is confusing. My initial post was talking about a specific built in sms app for Motorola and Google Android devices (and a few other OEMs that use the stock Google based Android Messages sms app) where the default sms app from the manufacturer is the only app not sending notifications when literally every other notification is still coming through.

If you could fix my post & title that would be appreciated since this is a specific but and not an issue with a lack of all notifications (please re-read my initial post. I detail exactly what is wrong)

---

@RicardoFitbit wrote:

Your reply is appreciated @pizzaboy192, sorry for the delay in responding your post.

Your mobile device isn't compatible because we haven't tested the device with our products and services to ensure that everything will work as intended. As per previously mentioned, because of firmware, Fitbit app, Android and device updates we cannot ensure that all your Fitbit features will work as the way they were designed. Please review our list of compatible devices and try with a compatible device.

If after trying with a compatible device you still experience the same situation, please contact me back. I'll be around.

---

,

[d_o_double_t]

I am having this same problem as the OP and have a compatible devise - Google Pixel 2. It is very frustrating to not have my messages sync to my watch 

[pizzaboy192]

For clarity since the moderator here can't seem to understand that this is a big issue,

The original post title was: all v3.0+ versions of app no longer send Android Messages notifications to Fitbit Blaze

Seeing as none of them are able to fix my post title, I may need to resubmit it, but at least this will appear in search results

[d_o_double_t]

Thanks for the heads up. I did notice that they seemed to ignore the fact
that you checked other phones and it's still an issue.

--
*Marnie 

Moderator edit: Removed personal information 

[Birch6]

I am having the exact same issue on a Samsung Galaxy S9. I have conducted all the same tests here beyond rolling back to an older version and gotten l the same behaviors.