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

New Garmin Connect version 3.13.1 only partially solves text message bug

Former Member over 8 years ago

The previous update of Garmin Connect introduced a bug where text messages couldn't be dismissed, from my Vivoactive watch. The latest update appears to initially to solve this problem, as the text message can be dimissed and it disappears from the watch.

However if the bluetooth connection is lost for any reason between the watch and the phone, when they reconnect again, all the text messages previously dismissed, appear back on the watch again. You cant even dismiss them for a second time.

Are other people who had this bug, experiencing the same problem after updating to the latest version of Garmin connect?

Thanks

Nexus 5, Android 6.0.1 / Vivoactive V4.40

0 Michalux over 8 years ago

Same here ;(
Still not fixed in 3.13.1. It's even worse. Before it helped to turn of text message notifications in GC (even for a moment) and turn it back again. Now even this does not work.

Michalux

0 Former Member over 8 years ago

Same here ;(
Still not fixed in 3.13.1. It's even worse. Before it helped to turn of text message notifications in GC (even for a moment) and turn it back again. Now even this does not work.

Michalux

Yes it does make it even more frustrating, now you can no longer toggle the notification button to dimiss them all. Rebooting the phone, is the only way I have found to clear them, which is a pain.

0 Former Member over 8 years ago

Yes it does make it even more frustrating, now you can no longer toggle the notification button to dimiss them all. Rebooting the phone, is the only way I have found to clear them, which is a pain.

I contacted Garmin support, who gave me following advice which has worked for me so far.

"I would strongly suggest uninstalling and reinstalling the Garmin Connect App. After you have done this re-pair your device with the app and the issue should now be resolved."