WFF-certification fails

Support
1

UPDATE!

The problem seems to be resolved.

I don’t know exactly what they did; I suspect they cleared the cache or somehow reset something within the system, but the two watch faces now passed through without any issues. And even an earlier watch face I mentioned now appears to have a WFF approval without me having republished it!

I hope things will go better from now on. It is these kinds of issues that rob people of their pleasure of participating in this otherwise wonderful feature.

This morning I sent this mail to Facer Support. I noticed that this is a problem lots of creators are struggling with.

Good day,

I am contacting you because I now have, once again, two watch faces that, for completely incomprehensible reasons, do not pass the WFF qualification.

Watch face 1: Coco Riga - CR Black Carbon Chrono - watch face for Apple Watch, WearOS, Galaxy Watch, Pixel Watch, Huawei Watch, and more - Facer
Watch face 2: Coco Riga - CR Blue Carbon Chrono - watch face for Apple Watch, WearOS, Galaxy Watch, Pixel Watch, Huawei Watch, and more - Facer

This concerns two watch faces that meet, in every conceivable respect, the requirements that Samsung can and may set for a watch face. I have only used standard, clean function codes provided by you yourselves for the hands, date, and any other function whatsoever. Therefore, I may assume that these are functioning function codes. And this is also confirmed by the green check mark in your Creator (Pro).

In fact, I have already published multiple watch faces with exactly the same setup. I even tried to get the watch faces through the WFF assessment using an exact copy of that one. I have also tried complete clean setups. Which failed in both cases.

The only thing that is different is the image of the watch faces. To rule out that the problem might lie there, I also used a setup with an already tested WFF-approved watch face. So with an approved setup regarding the formulas and watch faces used, but the watch faces still do not pass the WFF certification.

I have truly tried everything, even with the help of various AI machines, and adjusted everything more than once on the advice of said AI machines to remove every obstacle to WFF certification. Unfortunately, without result.

I have complained to you before about a watch face with the same problem. But firstly, it takes an eternity for you to respond, and when you did respond, in the case in question, you provided information about ‘a problematic function code’ that did not appear at all in the watch face in question. I have also informed you of this, but I have now been waiting for an answer for at least 10 days or longer.

I do not want to come across as too harsh, but I am of the opinion that this is unacceptable. I understand that quite a few creators are struggling with the same problem regarding the WFF terms.

It has now become a sort of gamble. You can do your absolute best to create a beautiful watch face, only to find that, for (a) completely incomprehensible reason(s), it fails the WFF certification and therefore cannot be synced by Samsung users.

Samsung is, as far as I know, one of the market leaders when it comes to mobile telephony and smartwatches. No WFF certification automatically means that your product is not eligible for the customers of one of the largest market leaders in the industry. And that is extremely frustrating.

I hope you can and will do something about this complaint. Both internally and towards Samsung. And naturally, I would prefer that this issue be resolved, because that is at the very least what you owe to your paying creators with a Pro account. Kind regards,

Coco Riga

2

If you enable inspection mode, someone may be able to peer review the formulas/syntax in your watch face. Maybe quicker than the support route.

1 Like
3

Done! :+1:

2 Likes
4

There’s no offending syntax contained in your attributes. Did the error message you get when publishing to WFF say Timeout by any chance? I have encountered lots of timeouts, and after 1 or 2 retries it usually publishes successfully.

1 Like
5

No time-out whatsoever. I’ve tried it numerous times with both faces and with countless setups and adjustments. It just doesn’t pass the certification for, as far as I can tell, no apparent reason at all.

1 Like
6

Something is not working right. Yesterday I had similar issue, tried to publish simple analog face with few datafields, and after long processing got direct message that it failed to comply with WFF and the face remains as draft, but in same time I got eMail with congratulation, that my face is live on Facer, which it is not.
I sent a ticket and while I am waiting for reply, sent the face for approval also on other platform.

3 Likes
7

Did you base these watch faces on a previous published watch face that was not yet WFF compatible?

I have had that issue. Support said it was not WFF compatible. That was not so helpful… So I risked publishing it without WFF compatibility anyway. Then I edited it again, and published it again this time with the WFF option. That then worked.

My old watch faces must have something in them that WFF does not like , but I cannot see it Facer Creator…

2 Likes
8

Heb het opgegeven met WFF of WTF als ze het niet publiceren dan laten ze het maar. En het ticket verhaal om er eentje in te geven nog minder zin in , want dan gaat de lol eraf en die is al even zoek. Moet ook al overgaan naar een andere browser bij momenten om hier iets te plaatsen en of te reageren. Dus als dat al niet lukt dan heeft de rest zeker geen zin. Als ik dan lees hoelang het duurt eer je reactie krijgt op je ticket tja…Er zijn hier enkele toppers en die echt behulpzaam zijn en in orde !

1 Like
9

I tried to publish again today, first a reduced version, then the original one and both went trough at first try without further change.

Maybe just give it another try in different browser or PC.

4 Likes
10

I had the same problem this morning, it is solved now.

3 Likes
11

No, I actually based these two watch faces on previous watch faces that are WFF certified. The two watch faces in question are, with the exception of a different ‘face’, identical to several watch faces I posted earlier that were published without any difficulty and received WFF approval.

I also sometimes experience a watch face getting stuck incorrectly at the WFF certification, but if I publish it again, it passes the certification after all. I know the system is a bit buggy. But I cannot get these two (plus another one that fully meets the requirements) through under any circumstances. I only get them published if I turn off WFF compliance.

12

Ik heb geen problemen met browsers e.d.

Maar het is wel duidelijk dat het probleem aan de kant van Facer zit. Of zat, want inmiddels hebben ze het probleem kennelijk opgelost.

13

Yup. They seem to have resolved the issue.

14

Odd. If I use less than a pixel of color, other than black or silver (which is basically gray) in the AOD the face returns not WFF compliant. I never had this issue before. So that’s a new one for me.

So, actually, you need to upload a different color subdial hands, for example, for the AOD version to comply with the WFF criteria. And I always thought that adding stuff would make the face heavier on the battery.