Hello,
I am a Pro subscriber and I have tried several times to publish a premium analog watch face design, but each attempt ends with a “Publishing Failed” notification.
All compatibility checks are marked with green checkmarks, and the only progress bar expressions used in the design are:
(clamp(#ZHR#, 0,200)/375)
(clamp(#ZSC#,0,10000)/19000)
Do you see anything in these expressions or the watch face configuration that might need to be corrected?
Or is there currently a known issue with publishing watch faces to Wear OS (WFF)?
Thank you for your assistance. I look forward to your feedback.
Best regards,
I know of limitations. For example
- if you have multiple expression in different fields of 1 element
- making the font size dependent on something like ZSC>9999, does not work.
- or having complicated nested expression in a text field may also work.
- or using DWE in an expression the pre check cannot detect.
Best would be to open up inspection, give us the link of your unpublished face, and people here can have a look…
1 Like
The first thing I see is that Facer doesn’t like spaces in expressions.
2 Likes
@terzydesign Hi . I was working in a ting with #ZHR# on it . and it has picked up Hiddent errors . Sometimes we have to start the Layers from scratch . I try using lots of () for solutions . I know it is childish but sometimes it works .
TRY
((clamp(#ZHR#,0,200))/375)
You could just devide #ZHR# by 375 to get the same result as far as I can see .
That Formula above published fine standing alone .
.
1 Like
77 bpm? You’re officially in relax mode.
1 Like
Yes . He He . I dont understand the devide by 375 .
1 Like
I was thinking about that also, I suspct that it may be intended for a circular progress element or fill meter with limited arc range.
2 Likes
here with my unpublished face link
Please let me know which part, make it error
hmmm… I do not really see anything wrong.
Except the battery progress: (#BLN#/125)100
The 100 should not be there.
You could also try changing battery text
from : #BLN#%
to : #BLP#
The “%” could be interpreted as the modulo function
1 Like
I think it should be there in place of the 125
1 Like