Don’t understand why this face: is showing WATCH FACE FOR WearOS, Tizen & WFF & this one: same thing but different color made from scratch (NOT COPIED) like the red version, Blue version shows WATCH FACE FOR WearOS & Tizen. This is really annoying as hell!!!
1 Like
Nice faces.
I wonder if it is server load or other connectivity issues as I have had 2 near identical faces updated, one errored of WFF and one didn’t but both showed full compatibility.
Another time I wasn’t paying attention and it only showed the 2 but was fixed after I updated it again.
1 Like
Still not working for me, I resaved it and published it and still doesn’t support wff. Taking forever for Facer to figure shit out. They should have had all the kinks worked out before going live with this new so-called WFF.
1 Like
It’s Beta and WFF went live before Facer’s new Creator. It’s confusing and frustrating i agree though. Things will be sorted - im afraid we have to be patient
1 Like
They do have a monumental task ahead of them and, personally, I like that we have what we do have and can report on any errors.
If you have a persistent failure with a face then you could copy the URL and raise a ticket. That will either help them troubleshoot an issue at their end, clear a corrupted cache related to the face or, maybe spot the tiniest typo in an expression that fails the stricter WFF code rules.
2 Likes
I understand that, but why not get everything fixed before releasing the new version.
1 Like
Because then we would have nothing to play with in the mean time.
And, of course, they would be short a few hundred unpaid testers ;-)
I’m OK with that. The more wild testing the faster issues are flagged.
Just had the same for my Binary V3, but in that case it may well be my custom FontStruct.
2 Likes
I think custom fonts may be a crapshoot just now. Just checked one that used another of my FontStructs that I updated and that does not list as WFF either, even though I have built a face with it in WFS. Font issues are likely to be among the hardest to nail down unfortunately.
Update:
Though I do think some custom fonts will be an issue I just did a rigorous repeat update of a face, cleaning all the fonts back to Amiko only and it still failed compared to a mostly identical face, where I just used a different battery gauge (actually simpler expressions on the failure).
I had already raised a ticket for one but added all my other failed faces and included the working sister face in the hopes it will help with troubleshooting at their end.
Side note: ceil() seems to be forking with WFF now :-D
1 Like
Oh . Bum . I thought .aab files were faultless.
1 Like