Charge 3 not receiving notifications using a Pixel 4a phone

[m_eastwood2]

I have recently got a Pixel 4a phone. However, Bluetooth does not recognize my Charge 3 so I can not receive notifications. The other features on my dashboard will sync with the phone. I need suggestions on how to resolve this or is it a lost cause. So frustrating. Do I replace my watch (hope not); do  replace my new phone (hope not)?

Moderator edit: subject for clarity/format 

[WilsonFitbit]

Hello @m_eastwood2. Welcome to the community forums! 

I'm very sorry for any inconvenience and thank you for the detailed information. Regarding your question, you don't need to replace your Fitbit device nor your phone, since there is currently an issue affecting syncing and notifications, and our team is aware of that and they are working to resolve it and find a resolution soon. Your understanding and patience is very appreciated.

On a side note, take into consideration that the Fitbit App works well with any mobile device that meets the requirements listed here. If your phone meets the requirements, then the inconvenience you're experiencing is due to the issue that was mentioned above. 

See you around. 

[m_eastwood2]

Thank you for your quick response. I appreciate it.  With the issue that you are referring to, would it explain why my bluetooth has never recognized my charge 3 in order for me to pair with it? I have only had the phone for 3 days and it has been a issue right from the beginning so I am wondering if the fitbit issue has been ongoing for that length of time..  It is an android with os 11 so according to the requirements link, then it should work.  I was not having any issue with my old Hauwei P30 lite.

[anwenkh]

 my android phone has recently stopped working for notifications also, but everything else is updating fine. So it may be a bigger issue.

[WilsonFitbit]

@m_eastwood2 Thank you for your reply. @anwenkh Nice to see you around and thanks for your input. 

@m_eastwood2 I appreciate the rest of the details and as mentioned on @anwenkh's post, we're currently experiencing an inconvenience affecting notifications and syncing. 

For more information and additional tips and suggestions, I recommend reviewing the following thread. Thanks for your continued patience. 

See you around.