I'm getting quite a lot of feedback on those past few days of users complaining that complications aren't updating anymore (they are stuck on a specific data and won't update anymore).
I'm not sure if this is due to a recent system update (feedback are mainly from Galaxy Watch 4 & 5 users) or from an OTA of the WearOS app on the PlayStore but there's definitely something very wrong going on.
Restarting the watch or switching to another watch face then switching back to the original face fixes the issue temporarily until it comes back.
This is affecting at least watch faces using the old support libraries, but maybe others I'm not sure. I'm not reproducing the issue myself on a GW5 running R900XXU1AWBA with WearOS core service 1.4.69.512673544 and PlayServices 23.06.17 but I got tons of feedback from different users around the world so it's definitely happening.
Description
Hey,
I'm getting quite a lot of feedback on those past few days of users complaining that complications aren't updating anymore (they are stuck on a specific data and won't update anymore).
I'm not sure if this is due to a recent system update (feedback are mainly from Galaxy Watch 4 & 5 users) or from an OTA of the WearOS app on the PlayStore but there's definitely something very wrong going on.
Restarting the watch or switching to another watch face then switching back to the original face fixes the issue temporarily until it comes back.
This is affecting at least watch faces using the old support libraries, but maybe others I'm not sure. I'm not reproducing the issue myself on a GW5 running R900XXU1AWBA with WearOS core service 1.4.69.512673544 and PlayServices 23.06.17 but I got tons of feedback from different users around the world so it's definitely happening.
Any help would be super appreciated.