I really enjoy using Facer, but it’s frustrating that designs show as WFF-compatible in Creator yet fail only after submission.
If this can be detected afterwards, it should be flagged beforehand, this would save designers time and keep them motivated.
Better pre-checks or clearer feedback would make the process much smoother.
I think they are going to fix that. Most of my designs publish for compatibility regardless of what I’ve been calling “the pink notification”. It may be a way of saying, “It will be published, but you did an override of a WFF compatibility notification.”
If you submit a ticket they may get to fixing it sooner.
In my creator (web) I have a green tick when during design it complies with WFF when it doesn’t comply it goes blue with an ‘i’ as shown below
I don’t know what happens after publishing as I haven’t got that far yet
I was faced with this several times now.
All green, but when publishing I get the error.
Perhaps there are some left overs somewhere hidden in the background, although I made everything compatible and deleted the rest.
I agree, @tom.vannes . I use a lot of custom fonts for testing the three operating systems for compatibility. I wonder if the system is detecting that and remembers what it didn’t like before I changed fonts for a final copy.
Probably unrelated, but I’ve been getting something that looks like that on several submissions. It just says error in submitting. I go back and do another update and no such message appears.
Like this evening. Don’t think it had anything to do with WFF given I get this same thing for faces that are just a face and hands. I’ll have to take a screen shot next time since memory obviously fails me.
There is a difference between what I was seeing and this as it turns out.
I submitted a new face and got that WFF warning in red pictured above. Several updates and it does not go away like the ones I usually see. I do not see the i in the blue circle pictured above in the editor.
Loaded it onto my GW8. Main face looks OK but it’s just a face image and two hands. The Roman numerals on the DIM/Ambient display do not render. Probably because of the conditional statements and tags I’m using. Or it doesn’t like the font I imported? No idea really.
Lord help me trying to make that screen in WFS. First, if any additional, step will be to get the center decoration on the main face changed to yellow.
Oh man, this is so amusing.
The original version of this last face loaded onto my GW8 but the Ambient screen didn’t work.
I decided to make an alternate version. I copied the first version, gave it a new name, and changed just the face art. That won’t load on my GW8 at all and the Facer app on my phone says it is not available while the first one says it is. Does load on my GW4.
Make sure the Watch you are trying to sync to is selected in Galaxy Wearable . I find it is a good Idea to have the correct watch model selected in the Facer App . If Creator is sticky I sync from My Watch Box on the Phone App .
Just double checked. AOD is on for sure, regular Facer version doesn’t render the Ambient screen with time in Roman numerals. Loaded another face first to make sure it went to the watch, it did. Then I tried the Facer Big Ben face, face showed but Dim face did not.
I made the same face in WFS and imported it to Facer. Both screens worked fine except for unexpected alignment issues with the Roman numerals.
Relevant here is the first time I imported the .aab file I got no red error as pictured above.
I changed the spacing on the text on the Dim screen and imported that version. I got the WFF submit failure above.
I did a resubmit and got no such error. Whatever is causing that flag is not working correctly.
Hi Folks,
I’ve been out of the loop for a few months and I’m seeing all this new WFF and Creator stuff. Wonderful! So I try it out and modify an existing face until all the checks are ticked:
I have come across this too. Could be that there is a “left over” font in your watch face or something else. Try saving it again and re-publishing it. Maybe clearing the browser cache and restating the browser helps, not sure…
I have this on several now.
I have tried stripping the fonts bare to Amiko and submitting on one of them that used a custom font, but with no joy.
I have another pair, both cloned from the same original but with slightly different battery dials and background images. One works, the other doesn’t.
What I have done is create a ticket including the URLs to all of the non working ones (and the working matched pair) to help the team troubleshoot why they are failing on submit.
It may be some artifact in the face, it may be a bug in the process, it may be they need additional incompatibility warnings but by including the non working faces in tickets we give them something to inspect to figure it out.
We had a creator update a week or 2 ago fixing several of the compatibility issues. Not sure when the next one is and I haven’t heard back on my ticket yet but I have another about the expressions not showing the result when correct and was informed this is currently in their test model and due soon so maybe more WFF issues will be bundled with that update too.
In my test Importing a .aab using Beta causes a Fail . So standard creator works fine .
I’ve not had that error - when all green it goes without issue. I guess I’m a lucky one so far…
Please take a moment to send our team a ticket about this experience you’re having:
https://help.facer.io/hc/en-us/requests/new
This will help the team investigate further and work out a solution!
Thank you for the help @tom.vannes @rob.fisk @russellcresser @thomasfmal.
Happens with either beta or standard current creator. I saw an update notification this morning that Creator issued an update that fixes some of the font issues noted. Font used is simply basic font within creator, nothing special. Still doesn’t work. Tried different browser, clearing cache, different computer all together - nada.
Thanks @Facer_Official, as you suggested I sent the team a ticket. I’ll wait a bit before trying to convert any more faces. Cheers!
Wonderful! Please let us know your ticket number so we can inform the team.
