i have a problem with latest Watch face Studio latest version when i generate watchface aab wihthout premade it generates fine.
But when i add 10x premade and then try to generate aab update it get gets stuck at 0% . When i open taskbar of windows i see no processes running by watchface studio. I made no other changes in watchface.
what am i missing
I am on Windows 10 Pro latest update
Watchface Studio 1.9.5
That’s not good, Ill test on mine today and report back.
well i tried 2 more apps. it went okay but when i try this particular app project it gets stuck at 0 percent
Those 2 others i installed on my watch 8 classic and tested Galaxy Wearable app and yes premade option worked fine.
I wonder whats up with this watchface WFS. i tried 4 x times this one.
The first one I tried got stuck. It seems that the more Premades you make, the slower it gets, but 10 seems to shut it down completely.
So I was backing down the number of Premades to see where it would start working, I got down to 8, and then this error appeared. Makes me wonder if there is some sort of corruption causing the issue. It’s too bad they didn’t trap for errors better in their code.
Today i reduced the 10x Premade Styles to 7 x Premade styles.
And this time publish 36 sdk aab worked great. I have submitted Sdk 33 and sdk 36 adb bundles for same watchface. lets see.
I hope to see the sdk 36 bundle appear when approved for Wear OS 6 watches and sdk 33 aab same watchface appear for Wear os 5 and below.
It would be nice if this bug should be fixed of crashing when adding more premade though. its a very nice option. Also if 3 x colors for styles can increase to 5 x sets that would make watchface studio more amazing.
I use the Memory checker Plugin to check the elevation of my File . That gives me this for a Photo Swap Face . But pretending to Publish it shows it is elevated yo SDK 36 .
.
Glad I am not the only one seeing this issue.
This is THE worst release of WFS we have had in a long long time
I agree with you.
I sent an update to a watchface with 2 x aabs
It’s been 1 x week and playstore has not approved it so far. today again I face error in generating with premades have to delete and bring it to 6 .
I am done with it for the time being this stable release seems more like a beta. I am staying aways from sdk 36 only aab generation.
For now I will not add sdk 36 bundles with pre made. It’s too much of work for too little.
Just so many things broken with the Premade addition
Typical WFS…. NO DOCUMENTATION and a lousy release. IMHO for development companies Samsung and Google are pretty poor at delivering
