The client has a Xiaomi Watch 2, WearOs4. After updating the watch face to WFS 1.8.10, the client, two of my already installed watch faces, began to behave inappropriately.
The screen on the smart watch constantly heats up and the watch face reboots. I will attach a video from the buyer, to illustrate the problem.
I advised resetting the smart watch cache, but the client claims that he cleared the cache for each individual watch face, but it did not help. He deleted and reinstalled the watch faces and the problem repeated.
But when he installed a new watch face, which was also updated in WFS 1.8.10, but had never been installed, there were no problems with the new watch face.
How to solve this problem? Is it possible to reset the entire cache on the Xiaomi watch 2?
Things he can try
1 - Restart the watch;
2 - Uninstall the watch face, restart and then reinstall;
3 - If the watch face is customizable, try to change one of the settings;
4 - Check if there is an update for his watch.
Things you can try:
1 - Test on a device (or emulator) to check if you can replicate the problem (if so, check the log);
2 - increase the version number, build the aab again and release an update, to check if the old aab had any problem;
3 - rebuild the watch face from zero…
Wouldn’t an update to Wear OS 5 solve the issues? Pretty soon Wear OS 4 and below are going to be left out, especially since Wear OS 6 is around the corner. Will Google Play even allow us to have “legacy” watch faces on Google Play anymore? If so, after Jan 26, 2026, we wont be able to sell them.
I am a xiaomi watch 2 pro user, technically it has the same features as the watch 2, if you want, I can install it on my watch as a tester and let you know the result so that we can understand whether the problem is in the watch or in the dial.
@Voron
would need more insight to say for sure.
Since you said, not all watch faces created using WFS 1.8.10 had the same issue. I believe it could be a problem on the specific device.
My suggestion would be to restart the watch, if it still persists maybe reset the watch and try again.
Hello! Reboots did not help. The problem is with those watch faces that I updated for the client to version 1.8.10. The watch faces that were already installed were damaged after the update. But when he installed my other watch face, which he never had on his device, the problem was not observed. This new watch face has also already been updated in the studio version 1.8.10.
No, I think Google will not allow selling outdated Watch Faces. Google constantly forces developers to update Watch Faces to the latest versions of their products. So people will always buy new smart watches because the operating system will stop updating on the old ones and they will not be able to install modern Watch Faces.
Right, so I am a little confused as to why you’re concerned about someone who is still using Wear OS 4 when Wear OS 5 has been around for quite some time now and Wear OS 6 is supposed to be released in mid-July?? I myself (and I am sure others) am currently in the process of updating all my faces that were not authored in WFS 1.8.7 before the deadline imposed by Google for Jan 14, 2026.
*** From Google***
From January 14, 2026: • Availability: Users will not be able to install legacy watch faces on any Wear OS devices from the Play Store. Legacy watch faces already installed on a Wear OS device will continue to work.
• Updates: Developers will not be able to publish updates for legacy watch faces to the Play Store.
• Monetization: New one-off watch face purchases, in-app purchases, and subscriptions will no longer be possible, but existing purchases and subscriptions will continue to work.
Action required:
If you currently use AndroidX or WSL to build watch faces, you must migrate to the Watch Face Format by January 14, 2026.
If you use Watch Face Studio to build watch faces you will need to resubmit your watch faces to the Play Store using Watch Face Studio version 1.8.7 or above: • Be sure to republish for all Play tracks, including all testing tracks as well as Production.
• Remove any bundles from these tracks that were created using WFS versions prior to 1.8.7.
I am sure I might be hearing from “clients” about how they cannot update their past purchases due to not having Wear OS 5+ but as far as I know, there’s not much I can do about it.
after the I read this situation, it was insane – the first-ever use other based watch