We also communicate with the respective team regarding your issue. The issue was resolved for the latest Watch binary, as previously mentioned this was a Google Wearable Core Services issue. Please check if your watch has the latest binary or not. And as you mentioned your users complaining that can be possible that your users are not with the latest binary.
If your issue remains please share your watch binary version with us. If possible please share a video and your watch Dumpstate log.
Looking forward to your response.
(Unfortunately, I was not able to create the dumpstat log because it was not possible to create it on my smartphone.)
I have been monitoring the problem since then and have not received any negative feedback from customers.
On my wearable app I only noticed that I sometimes have to try 2 times until everything is loaded. Additionally, customizing is extremely slow.
Yes, even on my side after 2 or 3 (or 4) attempts you can access the customization.
Sometimes it works without problems, other times not.
Unfortunately there is always some end user who does not understand certain things and deserves only a Casio from the 80s instead of a smart watch. There are those who write “it doesn’t happen on other watch faces” without understanding how things really are.
Yes I get it on your watch face as well as my test watch face frequently. It only happens in the Wearable App and not on the Watch itself.
Anyone know if this happen on watches other than Samsung?
Anyway they pushed a new Software update and maybe that fixes it (I said hopefully). If not report it to Developer Support as a watch issue and mention it is really a Wearable App issue. Any screen shots would be useful.
Hello everyone, the problem is still relevant even after the last update, users constantly complain about this, I remember when I bought the new Galaxy Watch 4 it was at the start of sales of such a problem, everything was perfectly configured through the application on the smartphone.