Lost notifications on Inspire3

[ElMeroMeroInge]

Recently lost notifications coming through from my phone. 

Tried restarting both devices, removing the tracker, forgetting the tracker on my Bluetooth, re-pair the tracker

The find my phone feature is not working, and neither is the test call.

I tried to switch to mirror my phone but that doesn't work either

Nothing seems to be fixing the problem. I noticed there was a recent update to the app, wondering if anyone else is experiencing issues.

[ElMeroMeroInge]

Downloaded/installed an mirror of 4.52 and the notifications are working again

Not sure if it's related to completely uninstalling the 4.53 app instance or if there is something "wrong" with the new update. Will investigate further. But glad I got it going again.

Google/Fitbit should probably run more QA on these updates

[Tiredbutbubblym]

Thank goodness I'm not the only one! I have gone through the entire process to try to solve the issue! 

[Mary4121]

Same here,  notifications not coming through 

[Lordgek]

I'm having the same problem. @google fix It!!

[Zann1209]

I apologize I'm not very knowledgeable when it comes to what you mean by you did a mirror of 4.52 and not the current 4.53.

When I look up Fitbit there's only one app.

[ElMeroMeroInge]

No worries, I'm having to use obscure language because when I initially posted, I was told posting this exact solution wasn't allowed 

There is "one"app but when they revise that app there is a new version which is the number. If you look at the Google play store the current version is 4.53.

So to solve it you need to uninstall 4.53, find a way to download the 4.52 package and install that older version. 

Then set Google Play to not update the Fitbit app until they fix it on their end

[kcrate]

When was the latest update?

From what I can tell it was back in spring 2025. If so, why are everyone's issues starting months later.

@google please fix!

[Zann1209]

Thank you. I believe I understand this better now. 😃😃Sent from my Galaxy

[MEG2025]

Okay this is coming from a very non-text savvy millennial how in the world do I find the older app in the Google Play Store

[Zann1209]

I understood what he meant by the older version but I, too, could not find the older 4.52 version. Google Play has only the 4.53 😞Sent from my Galaxy

[ElMeroMeroInge]

I can't find the changelog but looks like 4.53 went live on 7th of October. 

My device updated last week, I thought it was just I wasn't feeling the vibration on my wrist until Thursday of this past week

[ElMeroMeroInge]

So you won't be able to get an older revision from Google Play store, you would have to look elsewhere/be comfortable with that type of workflow. Sorry

[Traci127]

Do you have iPhone or Android?

Android hasn't updated on my end yet. They told me it's coming sometime this week though. I check for updates on my app daily. 

[kcrate]

Thank you. Working with an Android running 13 so according to the playstore
it should work.
States requires higher than Android 11.
I suppose time will tell.
Very frustrating and inconvenient.

[ElMeroMeroInge]

Yeah it's super frustrating, I use my Fitbit to cut down on my screen time, will only look if I see the notification on my Fitbit and it's important, otherwise phone stays in the pocket. 

[2012GLI]

Ironically 

[L_dawg]

The only "pure" older version (doesn't need an additional installer to install it) I found was 4.21 (took a little digging at that), but once installed and permissions/notification access are set back up, voila, notifications coming back through on the watch! (Imagine that...) Thanks for reminding me rolling back was an option, but unfortunately doing that is a bit challenging for less tech-savvy users.

[Traci127]

If you're satisfied by going backwards, to each their own. I'll wait until they fix the issue. And move forward to the new app. To help improve what's not working, point it out for them to know so they can fix it. 

Glad you found the fix for you. 

[kcrate]

Great if that works for you.
However, it should not be up to the Fitbit user to jump through hoops to
try to fix a developers error.
Updates need to be tested for every possible scenario before they are
released.