Context
I have developed a Wear OS watch face and published it on the Google Play Store. However, I noticed that the “Set” button is missing when viewing my watch face listing from a Wear OS device.
For reference:
Watch face A (another developer’s watch face) → Displays the “Set” button correctly.
Watch face B (my watch face) → Only shows the “Uninstall” button, even when the watch face is NOT currently set.
Does anyone know how to fix this issue?
hi uphoon,
Hello, thank you for your response!
The screenshot I uploaded was just a simple comparison image.
Here is the link to the watch face I created:
Since it’s a paid app, I didn’t directly share the Play Store listing in my initial post and instead used a general comparison image.
I have also tested a few other watch faces I developed, but I still haven’t been able to figure out the root cause of this issue.
I really appreciate your help and insights! Let me know if you have any ideas!
Hi uphoon,
How I would try to narrow down possible causes are:
Try to recreate the issue using different accounts on playstore or same account but different devices. To see if it is an account specific or device specific issue.
If all of them show the same issue I would try different watch faces to see if the issue is on the watch face.
Once we have an idea, what might be causing the problem then we may try to solve it.
Thank you! I will give that a try.
I have created a closed test.
If possible, could you check the app using the link below?
https://play.google.com/store/apps/details?id=com.fourcushion.wfsim
I have been trying various solutions, including modifying the manifest, but I haven’t been able to resolve the issue yet.
I really appreciate your interest and support. Thanks again! 
This issue first appeared in WFS 1.7.13.
I’m not sure if it has been fixed in the latest version (1.8.7), but 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, only “Uninstall / Refund” is shown, just like it was in the past in the oldest versions.
Basically, we’ve moved backward instead of forward…
Thank you for this new information!
I started using WFS from version 1.7.13, so I didn’t know that this issue didn’t exist in earlier versions.
I tested WFS 1.8.7 as soon as it was released, but the issue still persists. I quickly applied the update and rebuilt my watch face to test it, but the issue persisted. Because I have never used a version before 1.7.13, I wasn’t sure if this was a problem with WFS itself.
I really appreciate you sharing this information.
