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 .
This type of text-field formula, you used, often breaks under wff/wearos6. It’s very likely that this method no longer works there. The best step is to open an helpdesk ticket to confirm the limitation or get an official workaround.:
$#DOW#==0?Mon:$$#DOW#==1?Tue:$$#DOW#==2?Wed:$$#DOW#==3?Thu:$$#DOW#==4?Fri:$$#DOW#==5?Sat:$$#DOW#==6?Sun:$