Several times since updating to 2.25 and 2.26 the app uninstalls the wrong watch face and the list faces installed is incorrect. Restarting the app shows the corrected list of faces.
F7 Pro 15.77
Several times since updating to 2.25 and 2.26 the app uninstalls the wrong watch face and the list faces installed is incorrect. Restarting the app shows the corrected list of faces.
F7 Pro 15.77
For your information, you can contact Garmin - Chris
--…
FYI for those tracking the issue on their end, the issue has since been replicated using both the Android and iOS Connect Mobile APP.
I’ve also had it list the apps in the a different order. Sometimes the most recently installed watchface is shown last and sometimes first.
Similar issues here. What’s worse is two watch faces are acting like ransom ware. One just has a scrolling code to enter at a website and the only option is to buy the watch face. This is during its demo phase. I don’t want the watch face and now I can’t delete it! It’s taking up a slot and when I try a different hood watch face I like got deleted. If I try to reinstall the good watch face it shows as still installed with a message saying network connection error. If I try to uninstall it it just blinks.
This this feels like it’s malicious.
Reported here, but no mention about iOS, i'm concerned and using an iPhone ...
---
For your information, you can contact Garmin - Chris
---
Updated February 1st, 2024:
The issue is escalated to engineering to be resolved as soon as possible.
For anyone experiencing the issue willing to provide more information that will be given to our Connect IQ/Connect APP developers, please highlight my name and send me a Private Message. Thank you!
FYI for those tracking the issue on their end, the issue has since been replicated using both the Android and iOS Connect Mobile APP.
Awesome! Thanks for the update :)
Still happening on latest update :( :(
I've also had deleted watch faces show up in the Glances list. Watch needs to be rebooted to clear it from the Glance list.
Typically on an F7 Pro. I think it's happened on an EPIX Pro as well.
How is this not fixed in 2.26?!