Last week, when I would publish a new watch face, the watch face would fail to publish for WFF OS6.
I have seen this message before but the watch face would actually publish and was live…until last week. Now the new watch face is not live, just saved as a draft.
And some people do see the new watch face. I can see that they liked it on the notifications. So it must be live for some. This is strange.
As far as I know I am not doing anything different. And the only thing that is not compliant with the WFF OS 6 format is the date code. The message below that the leading 0 may not work correctly.
WearOS (WFF)
Date - #DdL#: This tag may not include a leading zero in this format.
On my Galaxy Watch 8 the date works ok.
I use the online Creator Pro on a Windows 11 PC.
The crazy thing is that I can use a different Windows 11 PC in another room and the watch face publishes just fine. Or, I can publish the watch face after midnight and it will publish then.
Anyone know why this is happening? It may be a cache thing, but I have no idea to fix it on my main computer.
So… anyone have a work around code tag for the date that will work with WFF OS6?
Or… why would my watch face publish on a different Windows 11 PC in the same house on the same network?
Is this a glitch from a Facer Creator Pro update?
Thanks for any help with this.
-Beth
If I am trying to publish a WFF / WOS6 I usexCreator Standard not Beta . I find it best if the correct Watch is selected in the Facer App .
Did changing the date not help? I do not think it is the computer itself unless your computers are running different versions of the same browser. Are you using updated versions of Edge on both?
For this remove the L : #DdL#: This tag may not include a leading zero in this format.
I didn’t think to try a different browser. Thanks for saying that. I use Chrome. I will try using a different browser. I will try to just leave the date off and see if that will publish. I will try removing the L in the tag also. Thanks so much for the info. I really appreciate it.
Thanks Russell for the suggestions. Right now I am not using beta, but I wonder if I am not choosing the right watch face format.
We have formulas to replicate Leading Zero . You want it for date Yes . I was doing that earlier .
.
$#Dd#<10?0:$#Dd#
Awesome, Thank you very much. I will try it.
You will see that it is quite good for any two digit number . If you want more zeros we have pad . For after the decimal pount we have toFixed .
Well I tried both tag workaounds and everything was green for Wear and WFF OS6, but still the face would not publish. I tried a bunch of stuff: tried a different browser, cleard my browser history, etc. I cleared other Browser things, flushed my DNS, but still luck. I can use the other PC and it updates just fine. I will contact support and see if this is a glitch with the updates. It is very strange.
Thanks everyone.
Did you try publishing from the Standard Creator ? Sometimes Faces pick up invisible errors . Especially if you have been reworking it . It is worth rebuilding it from the start . You have the resources . Some times you get invisible errors when you copy and paste Formulas . Type al Tag Formulas from scratch . Keep formulas in a Non formated document file like NotePad.
I have not tried it on the standard creator, but I will give that a go.
I also just use NotePad for all of my tags. I did try typing in the date tag, but no luck there so far.
I also published on my Android S9 Tablet and it publishies just fine.
So strange that only on 1 PC it is not publishing even though all formats show green compliant with Wear, WFF and Tizen.
Thanks for the great suggestions Russell.
On your Errant PC are you using the Web Creator or have you got the app running or is tha just for Mobile devices .
I am using the web app not a moble app on my PC. I usualy work on my main PC. I don’t think there is a moble app that you can use on a Windows PC. But my other Windows PC is the same. I use the web app on that 2nd Windows PC and my watch face will publish ok. I am using the same Chrome browser for all devices. On both PCs, the web app automatically updates to the latest version. Both PCs have the latest verion of creator.
I have a Samsung Galaxy Watch 8. My phone is a Samsung Galaxy S22 Ultra and I have a Samsung Galaxy S9 Tablet. All Samsung devices are Android Google Based. If I ever use my tablet with creator, I use the web app there. But the tablet publishes ok. I usually use Creator Pro.
It is just my main windows PC that seems to have the problem with creator not publishing. This started around the time of the last creator update. Before that my watch faces did publish ok on that main PC.
I just can’t figuure it out.
Which browser did you try? Do you manually update your Windows computers or rely on auto updates? Are both computers running the same build of Windows 11?
Hi, I tried Edge and Chrome browsers. I manually update windows. I usually hold off before updating windows right away to make sure the bugs are fixed. I did update my 2nd PC (the one that does publish my faces ok) to the latest windows update. But I think I was already publishing watch faces ok before i updated windows on my 2nd PC. That said, I will update my main computer and let you now if that solves the problem.
Thanks so much for that suggestion.
By the way, I absolutely Love your work.
-Beth
Well, I updated windows to the latest build 25H2 and it did not solve the problem. I was really hoping that was it, but no. Failed to publish message and only saved as draft… Even though all formats had green checks. Then I subitted the face on my Samsung tablet and it published just fine.
I want to thank you and Russell for trying to brainstorm and help me with this issue. -Beth
For me a good fix is clering the browser cache . But you have done that and you have to do all your Logins again .
I am no expert here but maybe i can add to the discussion. Firstly I understand that Edge and Chrome are more or less the same, so maybe try a different browser- Firefox or my favourite Brave.
Secondly it could be something internally in Facer for example this caused a conversion failure - The affected expression is:
((clamp(($#Dz#=ACDT?100;#Dz#=CEST?100;0$-0)/(100.0-0),0,1))*255.0)
It’s a bit strange because im 99% sure i didn’t use ‘clamp’ in the tag and more than that i couldn’t construct such an expression - i don’t have the know how.
What im trying to say is that Facer has been very flexible in how it treats expressions to date eg put brackets here, there and everywhere. Maybe we are being more forced to be more strict when constructing expressions.
Yes, Edge and Chrome are chromium based, but Edge is built into Windows and receives updates via Windows Update. Did both of your computers update at the same time in November? It would have been on or after Nov. 11. If I remember correctly there were about 5 chromium security updates this month. I’m wondering if WU changed something on one computer based on your apps and configurations on that one.
As for Facer, yes, I’m with BIELITZ in thinking that maybe we are being more forced to be more strict when constructing expressions.
Yes I have done that, and other ways to clear cache. But I am always ok to do it again. Yes you have to log in again, but that’s ok. I could definately be missing something obvious. Thx.