Also, it’s only useful in digital atm as you can’t use different pictures/hands for celcius and farenheit, so setting a decent scale is impossible…
ngl, a bit disappointed i have to wait to try/test new tags on my watch5
and also, i was kind of expecting there to be sunrise/set tags
1 Like
Yes . They have an WTHR_IS_DAY Tag . Not a big step to give us a time we could play wit. Oh Well . I don’t tHink they are Trying to Spoil us by giving us Too Much .
ahhh. well again, would be lovely to be able to try working with these new tags on my own watch
who knows when this update rolls out for previous models
just frustrated at the moment
1 Like
This New Stuff has Stopped Play all round .
1 Like
If anyone developing WFS should be listening, Sunset/sunrise times and wind speed would be a really good addition.
I remain adamant that a conditional line for Celcius or Farenheit is important right now, though.
Would also be good to be able to lock which day of the week a WF considers the first.
1 Like
I open a watchface, that was created with 1.6.10, in the new version 1.7.x. I wanted to send this to my Galaxy Watch 6 and it doesn’t work. I get an error message. This is not good. I haven’t used weather tags in the watchface. The Min SDK version cannot be changed. So I can’t use the new WFS version
Ooooof! Yeah I am definitely going to hold off. I was wondering if it’s possible to run 1.6.9 & 1.7.9 on the same computer? Or on separate computers (of course). I am just wondering if that would mess up the key store and directory stuff if you had 2 instances of WFS saving to the same place?
1 Like
I have already done several tests with projects opened with previous versions of WFS, but I have never experienced this error.
I have also successfully updated several watch faces opened with earlier versions of WFS, keeping the minimum SDK at 30.
I believe there is some sort of “delay” in WFS when automatically switching from 34 to 30 once the automatic project check is performed.
Normally, WFS performs an automatic check during the Build phase or when sending to a local device, and automatically switches to 30 if it doesn’t find tags that require API 34 (such as the weather tags / ranged complications in our case).
Try uninstalling and reinstalling WFS, or test it on another computer or virtual machine if possible.
1 Like
These requests only appears in a 2nd world / developing country.
I found the problem. I deactivated all the Range Value and it works. Problem … So I can’t work with it, my watch faces have Range Value … So I have to wait until Wear OS 5 has been distributed … Problem…not every watch gets Wear OS 5 … this is a step back
HI… new to the group.
I have been using the WFS for over a year now. I see in the beta version that there is an option to create coverscreens for the Flip 5 and 6. I have a Flip6. I attempted to connect to see the results on my phone… Low and Behold. Incompatible device.
Is there some sort of new way to connect the phone?
Thanks in Advance
Maybe this wild guess was right!
It would be interesting to see whether WFF2-specific features are actually being used in the RANGED_VALUE complications (or elsewhere).
This problem really ought to be corrected before the beta WFS is released for production use.
It is because in the Circle slots WFS automatically adds WEIGHTED_ELEMENTS complication type which is Wear OS 5 specific (API 34+).
I just created a new WFS project with a circular complication, and it did indeed publish as API34 (WFF2, OS5). However, I couldn’t find any reference to WEIGHTED_ELEMENTS in the .aab. But there was reference to RANGED_VALUE_COLORS, etc, which are WFF2-specific, so I now think that might be the problem.
The bottom line is that WFS1.7.9 can’t be used to create faces for OS4 if they contain a RANGED_VALUE complication (as someone else already pointed out). This doesn’t seem like a good arrangement.
1 Like
I had same problem. Simple fix. For now, just delete any of the new complications and you can run it normally So I removed all mention of weather tags etc.