Can confirm this issue on watch faces compiled with WFS 1.4.13. I am waiting for Play Store approval to see if this happens to my WFS 1.4.19 builds as well …
1 Like
Please respond when you have results. Thank you so much 
how come the [SC_GOAL] still won’t change if I change the step target from watch? This is because user may change its step goal anytime, so it should be flexible but not hard code it under project->settings->health
Can confirm this issue on watch faces compiled with WFS 1.4.13 . I am waiting for Play Store approval to see if this happens to my WFS 1.4.19 builds as well …
Just tested and this happens for watch faces made in WFS 1.4.19 as well. @catherina00 Could you please contact the Google Play Store about this? This looks like an issue in the Play Store app on WearOS 3 and WearOS 4 (tested both).
Sideloading the watch face via ADB or using the Play Store website works fine.
Hi, I am unable to connect to my Fossil Gen 5 (WearOS 2). My watch shows up but is grayed out…
I have my phone connected via usb to my computer, and enabled debugging over bluetooth in the WearOS settings.
Then I entered those commands in adb
adb forward tcp:4444 localabstract:/adb-hub
adb connect 127.0.0.1:4444
WFS 1.4.19 watch faces will only work on Wear OS 3 + (API 30+)
I notice that I cannot group complications(ctrl+g)(right-click group greyed out), I suppose the previous version can do that. is this a new change or a bug?
Check Q13 from FAQ
FAQ | Samsung Developers
Hi @catherina00 , just to confirm, is Google actually working on this or something different?
Thanks for you answer
Hi, is there any tag which can be used to get Calories from Samsung Health App instead of counting it via Steps ?
Hi! I wanted to publish my watch face, which was created with an earlier version (1.3.13), on Play, but it was rejected due to the reason ‘Your watch face exceeds the memory budget.’ Will the new version possibly occupy more memory? It seems like there is a slight delay when switching between the normal and AOD functions in the new version 1.4.19. Is this a known issue? Thank you
1 Like
Thank you for an answer instead, amoled
First of all, the latest version of Watch Face Studio doesn’t occupy own memory budget.
We all need to check the requirement of Google Play for Watch Face Format.
Please refer to this guide for optimization.
Watch faces created with WFS 1.4.19 are still not visible in Google Play because of the issue mentioned above. Maybe this should be stated somewhere in the WFS download page for as long as it is not fixed by Google? Publishing with WFS 1.4.19 does not really make sense right now.
1 Like
You means this?
- permission request (wear play store)
- watch face will also lose ‘install to watch’ buttons from mobile play store app.
- only way to install is through web version of the Google Play.
This is one of the things we informed for Google Play and we are also waiting to fix it. Because WFS 1.4.13 & 1.4.19 version were distributed, these issues of Google play have been found and are being improved. Please understand that it is a process to get better.
Thank you
1 Like
Yes, I wasn’t sure if this one was included.
Thanks for the update!
1 Like
Version 1.4.19 for Mac OS 10.15.7 won’t start. Get an error when trying to launch app.
1 Like
This feature requires Wear 4 (API 33) Watches. There is a Default of 6,000 steps See FAQ 11
Ron
Samsung Developer Relations
Hi! I wanted to publish my watch face, which was created with an earlier version (1.3.13), on Play, but it was rejected due to the reason ‘Your watch face exceeds the memory budget.’
I’ve notice that others are getting this too. It seems Play Store is cracking down on Watch Face sizes.
Be Sure to read these optimization tips But more importantly use a .png compression tools that can reduce the size of your images by as much as 80% (and the size of your watch face nearly that much as a result). I have no personal experience but there are many free or low cost options online and I had pngquant recommended to me it and it works freestanding or as a photoshop plugin.
It seems like there is a slight delay when switching between the normal and AOD functions in the new version 1.4.19. Is this a known issue?
There is always has been some delay you are pretty much changing watch faces but I think this may be more of a delay if using the WFS 1.4.19 version and running on Wear 3 instead of Wear 4.
Ron
Samsung Developer Relations
2 Likes
Please report this in a Developer Support Request and include all the system information and the error message or a picture of it.
Thank you for your cooperation and resolving this.
Ron
Samsung Developer Relations