This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Notification don't show up after 23.20

I updated to 23.20 on my 955 a couple of days ago- and since then the smart notifications are not displaying on watch.

I have tried unpairing and repairing my forerunner with my phone, besides toggling the notification settings on the phone throught connect and and watch itself- but nothing seems to be working.

The watch is connected to the phone, and I am able to successfully initiated "find my phone" from the watch and "find my device" from the phone, and the notifications show up in the Notifications glances as well- just that they do not pop on the watch screen like they did before the update. This is frustrating.

In addition- there is random severe battey drain issues.

Are these bugs in the update or could there be something else causing these issues?

  • Broke againPensive. Worked for a short while- not anymore.

  • And just like that- the notifications are working again. Also- the battery drain issue have disappeared as well. Grinning

  • I have exactly the same problem with 23.20 on my FR955solar
    fully connected Bluetooth to iPhone 

    have unpaired and repaired watch  

    rebooted both phone and watch

    Garmin connect notifications are exactly as they were prior to sw update  

    No notifications 

    are you saying fix is to factory reset my FR955?

  • Well- I would have said yes- but since last 2 days the problem has resurfaced. The notifications were working fine- and I did not change and settings on the connect app or the phone or watch- (The reset did not solve the issue- they started working randomly), but since 2 days ago- my watch lost the connection with my phone- on checking I found out somehow the connect app on my phone got signed out- I signed in again and the connection was established between the watch and the phone- but since then the notifications are broken again- plus the battery drain is back as well.

    This is definitely a bug which is causing the issue. Hope Garmin is listening and come out with a fix soon.