Do not get me wrong but when looking logically they limit complications to 8 that is to reduce ram memory i think, because watches get slower as ram memory can not cope with to many information.
Hi to all, great news my app is finally approved after 10th attempt, have had two animation 1st for dots in between digital time (2 images 0.5kb) and 2nd animation (15 images size 38.4kb) replaced 2nd animation with (6 images 26.4kb) and is approved now, it’s mean that problem is dealing with ram memory
Hi all. I get the same issue. First time I uploaded an analog face, with customizable hour / min /sec hand. The file size was 4,2mb. Next time I deleted the customizable hour / min hand (contained 7-7 .png hand) New File size 4,1mb. I uploaded this new file and its approved now.
Is it too many pictures or too many changeable items that could be the problem?
Another day, another update:
I removed everything except the time from the watchface and it was accepted. Then, i tried publishing an update, using a slightly more complex version (still really far from the original watchface) and guess what? Exceeds the memory budget. I optimized each and every PNG, reduced the color choices, reduced any customization to the bare minimum.
At this point, maybe this problem has to do with WFS. I published other watchfaces using the previous version, and I’m talking about really complex watchfaces, with 200+ frames animations, a lot and i mean A LOT of customization options and unoptimized PNG, and i never ever got a rejection, even recently.
I don’t mean to blame WFS or Samsung obviously, i just want to express my creativity without having the nightmare of working hard on a watchface just to be forced to demolish it to get it accepted
The funny part is that, if someone buys my watchface now, he/she will think it’s a complete scam, since it’s empty ._.
I went back to version 1.3.13. I will only use the new version when Wearos 4 is officially.
1 Like
Hi heard from the Watch Face Studio team.
This criteria is created by Watch Face Format which is included in Watch Face Studio v1.4.x, this is not caused by tool itself.
It is understood that many tool users have difficulties from this. So last week we requested Play Store improve the guideline about how to check, why to check, etc. again, but we have no answer yet. We’re trying to discuss to improve this situation.
Ron
Samsung Developer Relations
4 Likes
Sorry I couldn’t find the “storage space” option anywhere! When I open settings, I can see “Apps” section on my watch. But there is no “app info” or any other… Are you on beta version or something?
Thanks @r.liechty_SDR, this really made my day. I love WFS, really, and I appreciate all your efforts. And that’s why I’m really eager to use it to its full potential. I’ll patiently wait for any bad or good news then, even if I have an empty watchface on my account and I can’t update it 
You have to find your watchface in the app list, maybe somebody who uses English on the watch could me more helpful
I don’t see this in Galaxy Watch settings myself. I didn’t try the Android Emulator
Ron
Samsung Developer Relations
Yep, exactly. I had your same results. I guess we can only wait at this point
2 Likes
Are we sure that the new WFS is not at fault?
Yes I believe the Wear 4 Watch Face format is what they were talking about. That is even if you used Android Studio and Jet Pack with the same resources the Watch Face would use the same or more memory.
Maybe the WFS team should integrate a warning when the “memory budget” is exceeded as it already happens if we exceed the “8 complications”.
That as well as the 10MB size limit has not been allowed by Play Store since May 10th Wear OS Quality Guidelines
My guess is if you submit a Watch Face with 1.3.13 it is tested only on a Wear3 device but if you submit one with WFS 1.4.20 that it is then also tested on Wear4 device
Ron
Samsung Developer Relations
3 Likes
We hope to get more information and clarification, we are currently sailing on the high seas …
Thank you !
Edit: however, 10 MB of memory budget I haven’t seen since the 80486 (maybe it was something more).
BTW, my .aab file is about 7 MB.
1 Like
Update on my side: I remade the entire watchface in v1.3 (10 hours of pain) and published it. Accepted, no problem. And i put all the original stuff + more customization options. In the meantime, i received 3 one star reviews for the “almost empty” version, sadly. Nevermind, I’ll stick with v1.3 until v1.4 is 100% stable and safe to use withouth headaches.
1 Like
Same for me. Recreated the watch faces with WFS 1.3 and it was released after a few hours. No memory issues.
1 Like
Hi,
I moved to 1.4.20 and guess what ?
Reject 
but memory usage case issue is without SPLIT_BUNDLE, but I got information about basic funcionality that isn’t working as described - I just changed description and sent again, will see.
ABB file is 4 984 388 kb
Sorry to hear. @adrianrogalski . I got rejected for the first one, later approved for another four submission. I think it is the issue from google end.
@nobel.mixed did you chenge anything with watch face file or just submit again ?
@adrianrogalski i submitted again and rejected. Later i created new one and approved.
1 Like
Yup, this API Level 30+ thing seems haven’t been properly scrutinized. I guess I will downgrade back to WFS 1.3…
Yesterday I released a watch face created from scratch. Build and tested it on my Watch 4 and it functioned very well (but noticed the battery was running out faster than before). The app has 5 shortcuts, and 4 simple, straightforward text > tag expressions picked up from the menu. Build size 4.12 MB.
And guess what … 
1 Like
Hi. Maybe some TAG is causing this?
Which TAGS exactly did you use? Also, any bitmap fonts? These 5 shortcuts are complications?
Tomas