Hi All,
I would like to point out that lately I’ve been receiving several reports from users with Wear OS 4 that the steps and heart rate data on the watch faces “freeze” or not update.
They have to swap to another watch face to see that data again.
Thank you.
Are these from readouts with tags or from complications. And are they with watch faces designed or published with WFS 1.4.20 or WFS 1.5.7 or an older version?
Ron
Hi @r.liechty_SDR ,
from Tags, published with WFS 1.3.13.
At the moment I still haven’t had a chance to release watch faces on Play Store with WFS 1.4.x + due to memory budget issue.
Thanks.
The same problem i got reported today too. Users need to change the watch face to get steps and heart rate running again.
Watch face was made with WFS 1.3.13 and the watch face uses the heart rate and steps TAGS.
User: Watch 6 classic with WearOS 4
As I would have expected, we are receiving negative comments due to this bug…
Just to never rest easy … 
Happens to my calender complication also
Getting more and more of the same reports from users, HR and Steps indicators stop working randomly and can only be “nudged back to life” by changing watch faces. Noticed it myself, too.
Some users just leave negative ratings like it’s our fault (of course), but some are actually understanding and provide feedback.
Here’s the latest report I got from one user (Wear OS 4, Galaxy Watch 6, all sensor permissions allowed), might be useful for Samsung devs in troubleshooting:
“I also found out that if you leave your watch charging after 2 plus hours of charging after its fully charged that the bpm stops working. So far switching watch faces makes it work again. And Its a samsung thing not your products fault. Just letting you know.”
They have to reinstall the face. Happened to me right after I upgraded to one UI 5 on GW4
Hi Everyone,
I would like to keep this thread highlighted because I am receiving complaints about these issues on a daily basis.
I hope Samsung is working to fix these issues soon.
Thanks.
As far as I can tell they need to uninstall and re-install the watch faces have you suggested this?
Since WFS 1.3.13 is no longer supported I don’t think we can do anything about the issues as I do not think they happen with watch faces created by 1.5.7
I know you are not updating by the bundle size issue but that is Play Store Review issue.
If I’m wrong please correct me.
Ron
Samsung Developer Relations
Yes, of course I always say to uninstall and reinstall the Watch Face.
Yes, I can’t update the Watch Faces due to the big issue memory budget. I would be crazy to eliminate features and customizations on watch faces that have already been downloaded thousands of times , although I know that the same issue is also happening with Watch Faces compiled with WFS 1.5.7.
However, the experience is turning out to be very bad for the end user.
I honestly don’t understand these commercial strategies… There are more and more people who write to me who have switched to other brands asking me if I can develop Watch faces for those devices too… Which rarely happened in the days of Tizen.
I also encountered negative feedback and reviews on this issue, while it was not our fault.
WearOS4 comes with a lot of bugs that annoy developers, including heart rate measurement, problems connecting to watch face studio (you will need to spend more time and need to do it many times because debugging is not working. Debug wireless will turn off after restarting the watch)
We are forced to use the old version 1.3.13 because it is not possible to publish watch faces with version 1.5.7 due to memory error, the problem is still not resolved even after a long time!
What we need is a solution from Samsung and Google about the new operating system that also makes releasing a new version easier than it is now.
Sorry for complaining here, but if I send it to Google, I only get mechanical responses. They don’t seem to know how to review watch faces nor care about it. I’m really disappointed in them!
We hope the issue will be resolved soon!
Until now i got only complains about that “complications are not visible” issue.
Since my update to Wear OS 4 i got this issue on my Watch 4 classic too.
On my watch face (1.3.13) I have a 2 short text complications and one small image complication.
The strange thing is that one of these short text complications is always visible without any problems. The other two simply disappear for no visible reason.
If you switch to another watch face and then come back they are visible again.
What the heck? 
I also encountered negative feedback and reviews on this issue, while it was not our fault.
Correct and it isn’t Samsung’s fault either
WearOS4 comes with a lot of bugs that annoy developers, including heart rate measurement,
Most would say this is an improvement
Debug wireless will turn off after restarting the watch
It turns it off (or at least disconnects) after a period of inactivity. In previous version it would just kill the battery in hours.
We are forced to use the old version 1.3.13 because it is not possible to publish watch faces with version 1.5.7 due to memory error, the problem is still not resolved even after a long time!
This is supposed have been fixed apparently not all reviewers got the message.
What we need is a solution from Samsung and Google about the new operating system that also makes releasing a new version easier than it is now.
There are anti-trust laws that prohibit Samsung interfering with Play Store. Samsung can only talk to someone from Wear OS Development that talks to someone in play store.
Ron
Samsung Developer Relations
I do not know for certain but I read that if the owner uninstalls the watch face and then reinstalls after the Wear4 update that this resolves most of these issues.
Ron
Samsung Developer Relations
Hi Ron,
I installed this watch face after the update to Wear OS 4.
Also, @enkei_design wrote that this issue also occurred on a Watch 6 that was never involved in an update process from Wear OS 3.5 to 4.
Install, uninstall and reinstall for a newly purchased watch face sounds strange.
agreed, I know when run on device that unless you manually remove it there often is a caching issue that causes things like that. I thought maybe that was the issue with older watch faces when the OS is updated.
I can only report bugs that are with WFS 1.4.20 or 1.5.7 builds as WFS 1.3.13 is not a supported version.
I’d really like to know if anyone is seeing this with the WFS 1.5.7 version
Ron
Samsung Developer Relations
However, I would like to point out that many developers are unable to use WFS 1.5.x due to the memory budget imposed by Google.
I am totally aware this is not a Samsung problem but at the same time Samsung has released the new version of WFS which makes it impossible to update watch faces on Play Store.
With WFS 1.3.x there are no such problems and for this reason we are still forced to use this software version.
If we look at things from this side, it could also be a WFS problem (although we always have to blame Google) because with WFS 1.3.x we don’t have this issues.
This is a dead end where Samsung and Google should give us a solution without carrying out significant downgrades on the watch faces that we have released for 2 years now and which have been downloaded thousands of times.
I completely agree on this.
If Samsung can’t even talk to Google to resolve the memory error problem, then what should developers like us do?
If all face features are removed to be able to release it, then who will buy it? lol
And those who bought it will get an update about that change, they will get mad and accuse us of being their scammers!
Therefore, although we do not want to criticize anyone here, we need help from Samsung in connecting with Google.
Thanks Ron for listening and understanding.
For me it would be ok to limit the AOD in the new watch faces but I can’t gut the ones already released previously. It would be as if tomorrow Samsung updated its phones from Android to Symbian.