I published it in closed test, after installing the dial in google play, the adjust button does not appear, what could be the reaso
n?
n?
Why is it not automatically set as a dial when I download the dial to my wear os watch?
Hello Kerim,
Sorry for the inconvenience you are facing.
I would like to request you to report the issue to Google issue tracker first as Play Store is owned and controlled by Google, so you would get faster solution there.
I would also request you to share your solution here also, so that other members could get some help in similar issues.
Thanks for understanding.
Regards
Shamima
Samsung Developer Program team
2 Likes
No, this issue is caused by the latest versions of Watch Face Studio, not by Google Play.
And we don’t need to contact the Google Play team for this.
If you create a watch face using WFS 1.7.9, the “Set” option appears when installing a new watch face.
However, if you create a watch face with WFS 1.7.13 or later, only the “Uninstall / Refund” option is shown—just like it was in the oldest versions.
I had already reported this almost a year ago, but as usual, it was completely ignored.
We also discussed it here recently:
The Watch Face Studio team should kindly consider providing a quick fix on their end.
2 Likes
I’ll make my next watch dials that way then, but where can I find version 1.7.13?
I think so too, it’s a big shortcoming for an updated version. I hope they will solve this problem with the new update as soon as possible.
Thank you very much for your reply. @Matteo_Dini
downloadable versions 1.7.13 and 1.8.10 available 1.7.9 version required
I’ve shared Watch Face Studio 1.7.9 and you can download it from here:
NOTE: This is only a temporary fix because by January 2026, ALL watch faces will be required to be built using Watch Face Studio 1.8.x versions…
It’s essential that the Watch Face Studio team acts quickly to resolve this critical issue in the next release. @Shamima
2 Likes
@Matteo_Dini @Kerim @uphoon does it happen for every watch face built on 1.7.13 and above?
or there is a specific property that is causing the issue?
It was resolved for me only after switching to WFS 1.8.10.
1 Like