@amoledwatchfaces, Thank you for the link. I had not found that specific information yet. There’s not as much there as I would have hoped for, but that was not entirely unexpected. I’ll see what I can do with it! 
This is great news.
Will these new features also work on smartwatches still running Wear OS 3 or 4?
Kr Matze
@matze_styles4you these features are Wear OS 5+ only. I’m curious how exactly sourceTypes like WEATHER will be implemented in the new WFS. My guess is that when you try to add something like WEATHER.CONDITION, WFS will ask you about project change from minSdk (30,33?) to minSdk 34 (Wear OS 5), which will make this project not backwards compatible. That would mean WFS dev would need to keep two .wfs project files separately.
I may be wrong.
2 Likes
No backwards compatibility, for sure.
We are waiting for this!
1 Like
August is almost over???
1 Like
1 Like
I thought this might happen when they originally announced they were working on a new version to be released in August. 
I’m thankful they decided to release the 1.6.10 patch for us with the SDK 33 target update rather than making everyone scramble to meet Google’s deadline when they finally do release this one.
New beta version just got released. Do I have to be scared to try it out right away?
2 Likes
The new version 1.7.9 targets SDK 34 (Android 14). From what I understand, older watches like the Watch4, Watch5, and Watch6 won’t be compatible with watch faces created using this version.
On the other hand, the previous version 1.6.10, which targets SDK 33, is compatible with all watches (4, 5, 6, 7), but it lacks new features like weather conditions and gradients.
Is this correct?
1 Like
The good thing about WFS from my point of view is it can be rolled back to the previous version . I will give it a test for my GW5 .
1 Like
So, how do you roll back? Do you install the new version 1.7.9 in a new directory on your computer and leave 1.6.10 as it was?
1 Like
I have actually made copies of the .exe files . but I think they are on the Site as well . But I have to say I am no expert so please check .I don’t know what might be changed re Lisences in the Default folders .
I know someone who tests new WFS on Another P.C. It is quite possible that these can both be on the same system . Since I do not publish my own work I have not much to lose . But since my Watch is on OneUI 5 , WOS4 at the moment I might give it a miss .
No, there is no SDK 34 target on the new WFS.
The min SDK is 30 and the target is 33.
This means that there are no compatibility issues on Watch 4 and later.
A separate discussion for the Weather tags that should be compatible only with the new watch face version 2 (Wear OS 5.0 +)
2 Likes
Additionally, it is mandatory to use Watch Face Format for all watch faces published in the Google Play store from early 2025 (the exact date will be announced in the 4th quarter of 2024).
Does it mean, we won’t be able to publish watchfaces for older devices anymore in the 2025?
It’s similar to Tizen back then. @unions8
But when you hit Publish on the new version 1.7.9 you see min SDK version 34+ and you cant change it.
[EDIT]
hmmmmm… this happened when i opened an older project.
When i create a new Project i see now MIN SDK 30
I believe you might have some sort of glitch on WFS.
The min SDK 34 is only set if you’ve added the new Weather tags (or ranged complications).
Otherwise, the min SDK 30 should be shown.
Try waiting a few seconds after you’ve requested the build / you hit on Publish. It should switch from 34 to 30 after an automatic check.
3 Likes
So Using weather tag now would not be right option. and we should wait till older devices get update to wear os 5…