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.
I will try a few other browsers as well.Thx for that. Most tags are generated by facer creator. Like the date tags for instance. But when using the Date tag generated by Facer, I get the leading 0 error message. As of a couple of weeks ago, my watch faces would still publish live. Now they don’t, but only on 1 device. I got a couple of Date tag suggestions:
$#Dd#<10?0:$#Dd#
For this remove the L : #DdL#
They work, and the leading 0 message goes away and I get green checkmarks that the face is compliant with Wear, Wear WFF, and Tizen Platforms. I don’t use Apple so my face does not comply with that platform. But any watch face I publish, The face will only save as a draft, not live.
I could be missing something simple and obvious, but just can’t think of it. I don’t know a lot for sure.
As far as I know every device I use is up to date with browsers and main updates. I update Chrome manually many times a week. I do remember that there were some security updates to attend to right away. But I will try a few other browsers to see if that may be the problem. Thanks.
@photobeth . I think it is time for you to show us your Draft . On of us might spot something other than the Leading Zero thing . You might see if you are following the other Topics I have tested
.
$#Dd#<10?0:$#Dd#
.
On its own as a publication .
.
Rusty, actually I believe all of my Watch Face designs are open to be viewed. This is one that I updated yesterday. It was created a while back and I was updating it to get it compatible with WFF. I did get it to publish by using a different devise.
Thx
Well I see I am not the only one with this frustrationg head scratcher problem. I am lucky that my faces will publish on a different device.
I am curious what is the real problem, if it is the last Creator update or something internal to our devices. I just have no idea.
@photobeth some have reported an error with #BLP# try #BLN#% . You have mad a lot of extra work doubling your Layers for AOD . You only need to do that if they are changing .
ok I will add this tag to my files and try it. Thank you.
Now you see this is where I really am a rookie. I didn’t know that about duplicating with AOD. Thanks for that info as well.
I tried publishing 2 seperate watch faces on Firefox and Brave, no luck. Both only published as a Draft . I was then able to publish both on another device.
All browsers, Windows Operating systems and Samsung devices are up to date.
It is maybe possible you are confusing the system swapping from one System and Browser to another . Concetrate on publishing on the PC and Browser that has worked . I only publish from one Laptop .
Well I’d like to use my main computer as I have been using for a while now. My main pc is at a desk with a fast processor and my image files are connected. I have a large sharp monitor there. It is just better for editing. My 2nd pc is for streaming and it is far away form where I sit. It is slower and not the best for editing. For now I will edit on my main PC and then publish on my 2nd pc or a differnt device. Hopefully this will all sort out.
I am really clutching at straws and I am no expert . But it seems PC2 might have the Prioity connection to your Router . I am thinking run the Facer App on PC2 and the Web Creator on PC1 . I suppose your streaming PC is connected LAN and the Main PC WiFi .