I have 6 projects with hundreds of users
all are stuck in 33+
I open the WFS file and attempt to publish as sdk34
Can not change the sdk level
What gives? What do i have to do?
Cant open 2 projects and copy an paste
So what is the real answer?
WHY WHY WHY are google and Samsung so inept at development???
am i to understand that the Min of 33+ and Target of 34 is acceptable?
No one here has been able to (or won’t) answer this question so far. I assumed that as per Samsung/Google, it only publishes at 34 if built in weather or edge complications are used. If not, it publishes at 33+. Someone here told me that WFF /Wear OS6 is a hard API 34 so who knows what Google/Samsung are doing? I guess we just all have to sit on our hands as usual and wait for Google to tell us we need to update all our faces once again…or not? Who knows…
What I can say is that since the Aug 31 deadline. My sales are at about 1/4 of what they were…I have updated all my faces (1.8.10) and been given notices that I have addressed the latest policy issues but even getting those assurances from Google doesnt give me any comfort.
The easiest way is to activate the Heart Rate function (by enabling it in a small-box complication).
Sorry, I am not understanding what this has to do with API 33+ vs. API 34? We’re trying to understand why we cannot publish at API 34 for watch faces that do not use some new features such as built-in weather or edge complications and are only able to publish at 33+. So we are wondering if that is something to be concerned about since WFF format is strictly at API 34 according to Google.
What google requires is targetSDK.
TargetSDK is just to say that you developed your watch face focusing on that API level. Google always requires this for “security” reasons, as new level of the API means “better security”.
MinSDK means the minimum version of Wear OS compatible with your watch face.
When you rebuild your watch faces using WFS 1.8.x you get the target set to 34, no matter what you do, the targetSDK is always 34. You can check this in the picture of the person who asked the question at the top, or at any published watchface you updated with the version 1.8.x.
The 33+ and 34 showing on the WFS is the minSDK. Some features, like weather (introduced on watch face format version 2) are only available on API 34. If you use those kind of features you watch face will not work on devices that does not have the WFF version 2, like the devices with API 33. However, if you dont use features from WFF version 2, you can build you watch face using the version 1, which is compatible with devices using the API 33, 34 and greater.
The value you see on WFS or the minSDK (also in the picture) just means the minimum wear os version compatible with your watch face.
33 = Wear OS 4
34 = Wear OS 5
35 = Wear OS 5.1
36 = Wear OS 6
And the WFF version compatibility
WFF 1 - 33+
WFF 2 - 34+
Samsung setting the minSDK to 33 (“33+”) is to allow more devices to be able to install your watch face. Setting to 34 means that watches with Wear OS 4 will not be compatible. But, again, no matter the “33+” or “34” on WFS, your watch face (built using WFS 1.8.x) is with targetSDK 34, which is the minimum required by google at the moment.
My understanding is the same as dect said.
All watch faces built with WFS 1.8.x will automatically target API 34 and comply with the latest requirements.
Here’s a quote from Google’s “Action required” email that confirms this:
”…Google Play requires all apps to meet target API level requirements before Aug 31, 2025.”
I also remember that one part of Google’s explanation about this in Play Console specifically stated that watch faces need to be built with WFS version 1.8.7 or newer in order to comply with the latest requirements. I can’t find this exact message anymore, but I am sure this was mentioned.
Therefore, as long as the watch face is rebuilt in WFS 1.8.x, you should be good in terms of the latest requirements.
That is, until those requirements change again, likely next year 
Thanks very much for your detailed and informative explanation!
THANK YOU SAMSUNG
the new upgrade should take care of this
The new WFS version 1.9.5 only allows publishing for target SDK 36, only supports 8 watch models, please help anyone.
I am using mac, can anyone provide link for version WFS 1.8.10 download
[Update]
I removed the premade and then the target SDK was set to 33 
Actually it’s WearOS 6, not just Watch 8s. My 2024 Ultra with WearOS 6 is working fine with the new APIs.
