Sense 2 notifications are not working

[Samsay]

Since the latest Sense 2 update (v 60.20001.220.31) and app v. 4.65, my notifications have completely stopped working on iOS 26.3.1. The notification settings page in the app is totally blank. I’ve tried restarting and reinstalling everything, but no luck. Also Alexa setup is not successful. 
Everything was working before updating Fitbit app and firmware


Moderator Edit: Clarified subject

[MarreFitbit]

Hi there, @Samsay. It's nice to see you around the Fitbit Community Forums. 

Thanks for bringing this to my attention. I appreciate your messages and feedback regarding this issue regarding the blank screen in the app notifications setup page. We‘re taking your comments and sentiments in regards to our products and services into consideration.

As a moderator, I'll be posting here any news as soon as I get them. 

Meanwhile, always keep your devices and application updated. 

[Samsay]

Hi MarreFitbit, 

Thank you for the response. It is encouraging to hear that the team is taking this into consideration. Given that many of us are now unable to use core features like notifications, Bluetooth calls, and Alexa, I look forward to seeing a formal fix in the next app or firmware release. I will keep an eye on this thread for your next update.

[farrellcsun]

The langauge setting workaround helps with the notifications, but still no joy on the Alexa setup.  Hoping they fix it soon! 

[Samsay]

Hi Maria,

I have found a very specific and reproducible bug in App v. 4.65 that I hope you can pass to the developers. This is a region-localization error, not a hardware failure:

• The Discovery: When I change my iPhone Region and Fitbit App Location to 'United States', my app notification list immediately jumps from 3 apps to 13 apps.

• WhatsApp Case Study: While set to the US region, WhatsApp appears in the list, and I am able to receive both notifications and WhatsApp calls on my Sense 2 perfectly.

• The Bug: As soon as I switch my settings back to Australia, WhatsApp and the other 10 apps disappear from the list entirely, and the notifications/calls stop working.

• Alexa: Unfortunately, the Alexa setup still fails with a 'Couldn't connect' error even when the region is swapped, suggesting that might be a separate firmware communication issue.

Since the features clearly work when the app thinks I am in the US, it seems the Australian localization in v. 4.65 is accidentally filtering out these core apps. We really need v. 4.66 to fix this regional filtering bug so we can use our devices normally in Australia again.

I hope this specific detail helps the team speed up the fix

[Aura23]

Hi Samsay, try setting your Fitbit language (Settings > Apps > Fitbit) to "English". If you do not see the language option, first add any second language in your Language & Region settings, then you should see the language option for Fitbit. 
See here: https://www.reddit.com/r/fitbit/comments/1s3euj0/psa_if_the_app_notifications_list_is_empty/

Then check the 3rd party apps' language settings as well. I think the apps' language has to match the Fitbit app's language maybe.

Good luck

[Samsay]

  

 

 

Hi Aura23,

Thanks for the suggestion! As you can see in my settings, I've already set the Fitbit app language to 'English' and my region to 'United States'.

This is exactly what triggered the fix for me—my notification list jumped from being empty/blank back to showing all 11 apps, including WhatsApp. I can confirm that as long as I keep these US/English settings, WhatsApp notifications and calls work perfectly on my Sense 2.

However, the moment I switch the region back to Australia, those options disappear again. It seems v4.65 specifically struggles with localized regions like Australia. Also, even with these settings, the actual Alexa setup still fails with a connection error for me, so that part of the bug seems even deeper. Hopefully, this helps others who are stuck with blank screens!

kind regards,

 

[Aura23]

Oh weird. My region is Canada and my system language is English (UK) but I had manually to set Fitbit to English (not English UK or English (Aus)) _after_ setting system language and region. 

Have you tried that specific order? After setting region back to Australia and system language to English (Aus), change Fitbit language to any other, and then change it again to "English" (not any of the variants)

I'm only curious if it makes a difference but of course, no stress if you don't wanna do all that! 

[Samsay]

 

 

just did some more testing with the regions, and the results are really strange.

I found that if I set my region to Egypt, the notification list works perfectly (11 apps visible, WhatsApp included). But the moment I switch it to New Zealand, the entire list goes completely blank again—exactly like it does for Australia.

It seems like v4.65 has a major 'black hole' for certain regions (AU, NZ, etc.) while others like the US and Egypt work fine. I'm currently sticking with the English (US) language and Egypt or US region just to keep things functioning.

I haven't tried the specific toggle order you mentioned yet because I'm afraid of losing the WhatsApp connection again, but your theory about the app getting stuck on specific regional variants seems 100% correct. This is definitely a widespread localization bug!"

 

[Samsay]

 

[farrellcsun]

Appreciate all the additional testing you did!  Bottom line - we shouldn't have had to spend all this time on it and finding workarounds - it was all working fine right before the latest update?!  Why couldn't they just roll it back?  Anyways - still waiting for an update to address the Alexa set up error as that was also working perfectly before, and now not.  Probably related to the localisation thing too.  Thanks again!

[Samsay]

Truely We have wait on a real fix for the notification and Alexa. Hopefully, version 4.66 sorts it out.

[asiayeah]

Yes. I’m still waiting for 4.66 or later to fix the Alexa issue. It’s been failing for more than a week unfortunately. 

---

Fitbit App 4.66 is now available for iOS but I’m still having the same Alexa issue. 

[farrellcsun]

Thanks for the heads up about the app update.  Sadly, yes I updated the app to v4.66 as well and no update on the notifications bug or Alexa set up errors.  This update did not address either of the issues.  For the notifications, you have to continue with the "workaround" for the temporary fix.  I'm re-opening my google ticket to let them know neither issue was fixed with this update.  

[Samsay]

 

That is so disappointing. I’ve just updated to v4.66 as well and can confirm the same—the update fixed absolutely nothing. I still have to use the English (US) workaround to see my notifications, and Alexa is still giving the same connection error shown in my screenshots. It's frustrating that such a major bug is being ignored in these updates. Thanks for re-opening your ticket; hopefully, if enough of us complain, they'll actually listen!

[farrellcsun]

Yes - exact same.  Ticket reopened!!  This ticket encompasses both the notifications issue and the Alexa connection error.  Take me back to v4.64!!

Recent case
We're working on this support case for you
Fitbit Notification not received
Case ID X-XXXXXXXXXXXXX                                        In Progress

                                                                             Last updated 1 hr. ago

Moderator edit: removed personal information

[AJSim]

Just came to here to say the same thing.  I am having the same issues with the Notifications and Alexa.  App v4.66 made no difference.  

[Samsay]

Just updated to v4.66.1 and I can confirm Alexa is still completely broken.

Despite the update, I’m still getting the exact same 'Couldn't connect' error every time I try to link my account. It’s disappointing that such a core feature of the Sense 2 has been left non-functional for weeks now. Has anyone actually heard from a Fitbit moderator if this is even being investigated as a regional bug? It feels like we're being ignored.

[farrellcsun]

Yep, just updated to v4.66.1 and same, notifications still buggy without the workaround and Alexa error on setup.  I got the following update from my Google support ticket yesterday: 

"Thanks for reaching out to the Fitbit Customer Care Team. We appreciate you sharing this information.Thanks for letting us know about this issue. We’re aware of it and are working to identify a resolution as quickly as possible. We're sorry for any trouble. We appreciate your patience and look forward to getting you back on track."

Not exactly confidence inspiring...

[Samsay]

Classic generic response! It’s disappointing they keep releasing these minor updates like v4.66.1 without actually fixing the Alexa error. Thanks for sharing—at least it’s officially on their radar, even if they aren't moving fast.