Update: WFF Compatibility Issues After Update

An update: users reporting multiple problems with WFF after the recent update:

  • Faces marked with the green check and WFF logo still break after syncing.
  • Time alignment is totally off on the watch but looks fine in the editor.
  • In some cases, the time is missing entirely, even though it should work per the compatibility document, using the right formulas.
  • The editor is no longer WYSIWYG, and the error checks/compatibility indicators don’t match the actual result.

Users syncing these faces are reporting these issues.

1 Like

It seems like the Font we use has become critical . Do not use the Facer / Fixed Width / Apple Fonts .

1 Like

Too many issues atm with WFF publishing (unless using imported aab file). Even basic BPN tag is not supported which is an essential tag and exists in WFF. Facer need to release a hotfix urgently to keep faith. They must have seen a massive uptake on premium subscribers in recent days and they are not exactly being communicative on issues.

The other day i tried Watchmaker for OS6 and was very impressed. It works fantastically. However, no support for complications with Samsung watches which I hope they rectify. But it was interesting to see the way they have implemented their creator app vs Facer and was much more intuitive to use.

2 Likes

Thanks! Right now, I design my faces in my spare time on an iPad, mostly during lunch and coffee breaks :grin:, so I can’t test it yet. I’m planning to install it on my PC at home, make it accessible via my iPad, and then try designing in WFF and uploading the AAB files. I feel like Facer rolled out this update a bit too quickly, which could lead to more complaints and hurt their credibility, a shame, because I really like the platform (I’ve been using it for 6 months now) and hope I can keep creating like this!

1 Like

Thank you, I’ll check that. Hopefully, it will fix the font issue. In the photo someone sent me through the Facer review system, the font appeared much higher than it does in the editor or on my older smartwatch, so there seems to be a difference in line spacing with WFF.

1 Like

When you say you are Designing in WFF . Are you working on Android studio or do you mean WFS ?

1 Like

No I tested out WFS studio, but can not access it with my IPad during the week. In weekends and spare time when I am at home I try to reverse-engineering how to manually repackage a valid AAB for Watch Face Format without relying on Android Studio or WFS. The challenge lies in replicating the compiled resource table, manifest indexing, and protobuf metadata (BundleConfig.pb , resources.pb`) that are normally auto-generated by the Android build system.

1 Like

Are you saying you can build a .aab file from stuff made on Face Creator ?

1 Like

No, that’s not what I meant. I first want to determine if it’s possible to repack a WFF file into a working AAB without using Android Studio or WFS, but I’m still in the very early stages of understanding and figuring that out.

1 Like

Have you tried loading a wff file into an AI and asking it to convert it into an aab? Cheating i know…but i bet it can do it

2 Likes

Yes I use GitHub Copilot for a long time, but this a tough one, have contact with some code wizards, my knowledge on coding is good but not on top level.

2 Likes

Hi all
I was not really bothered about WFF and compatibility. If I really want to create a watch face being compatible, I have to live with the current state.

But it seems there are things that are not flagged in the Facer Creator Reference.

The font being one thing I am getting complaints about. Anything else of concern?
As long as I could be faced with unforeseen things, I am hesitant to publish anything…

3 Likes

If you are publishing watch faces for WFF, you really need to have a OS6 Watch to test it on, as the Preview is not representative of what is published any longer.
Otherwise, best to untick the WFF tick box on publishing and stick with the legacy options.

3 Likes

Yeah, plenty of issues. I had this simple formula (pad(#Dm#,2)) combined with (38 + (sin(rad(#DWFSS# * 60)) * 2)) , and I’m getting complaints that it’s not showing on Wear OS 6. According to the compatibility list, these shouldn’t cause any problems?

2 Likes

Yep so true.

2 Likes

Right now, nothing seems to be working on WFF. users have taken wrist shots and not even the hands are showing, no weather or health data is showing and digital time alignment has been reported as being out. I am not bothering with WFF and I deselect this option before publishing. I am also placing a disclaimer in my designs going forward because I am swamped with complaints from ULTRA 7 users.

3 Likes

I am thinking of doing the same (disclaimer) but what would be a good disclaimer text?

1 Like

I will just simply say that this design will not work as intended on the ULTRA 7.

1 Like

Just untick the WFF option. Then it cannot be synced to OS6 wear watches

2 Likes

I have actually seen the opposite. I like @kvansant 's idea with the watch face titled “B# - Metro 5 WFF

and in the description it says, I quote:

“*** PRE WearOS 6 users should sync the face called “Metro 5” to get many additional features not available on WFF watches.”

2 Likes