Wear OS, Play Store | Memory Budget

Watch Face Studio
21

However I keep wondering why if we compile the watch faces with WFS 1.3.x it is accepted without problems. …

2 Likes
22

Exactly, the specifications are the same. Yet it’s swiftly approved via WFS1.3.x but not with WFS1.4.20

1 Like
23

Thank you for the info.

24

WFS 1.4.20 created watch faces have something like two versions bundled.

One for API between 28 and 30 and other one for API 33+
The second one is using Watch Face Format.

First one, which is being reviewed by Google systems is running in some compatibility mode or something similar…so this new watch face can still run on older devices (with API under 33). I think there is the issue.

I think two or three things may happen in the future.

  1. Google will start reviewing apps on Wear OS 4 devices when there are first Wear OS 4 devices, so watch faces will pass reviews because they will run on Watch Face Format
  2. Google will adjust memory budget limitation
  3. Watch face studio next version will somehow correct memory usage as there are no issues with 1.3.13 created watch faces.
2 Likes
25

Keeping fingers crossed :yum:

26

Good to know. thanks for the info.

27

Hi All,

Is there anything new on this side?

I’m always getting this error when trying to update a watch face with WFS 1.4.20 (no problem with WFS 1.3.x - size of the watch face 3 MB):

MemoryBudget
MemoryBudget1582×915 141 KB

???

@r.liechty_SDR

Thanks !

28

There was a meeting about a week ago Where Samsung expressed the importance of this and asked for a change in policy or a guideline on the size that is demanded for Wear6 watch faces. I’ve asked for an update on the matter.

Ron
Samsung Developer Relations

8 Likes
29

Thanks a lot Ron !!!

30

Hello, I got watch face rejected, too. It said my WF exceeded memory usage. But my .aab was 7.95 MB. So I made a .zip, extracted the files and checked the siza again. It was 13.4 MB. So it exceeded. I tried to rebuild the WF, still the same outcome. The size was to big. So I checked every single file in the build. One of the pictures in resources had size of 4.48 MB and it was 1930x2250 px. But I shrinked that picture to 250x 290 something in watch face studio, so why did it stay so big???
I took that particular picture used affinity designer to export it in small size (250x290 px) and used it already shrinked in the watch face studio. And this worked. My watch face was approved within 3 hours.

So if you use biger pictures in watch face studion and you shrink them in the program, the picture will be still saved in your build in its original size and this might be the issue. Take a look at your resurces and shrink them before you start to build the watch face in watch face studio. This worked for me, maybe it will work for you, too.

1 Like
31

Thanks for sharing your experience !

In my case, I always use images natively scaled down to 450px (compressed) and my unzipped files are always under the 10MB mark but Google keeps refusing updates (BTW, NO problems with WFS 1.3x).

2 Likes
32

I got the software for free and I didn’t pay Samsung for the software.

33

Dont worry, we paid it for you :slight_smile:

1 Like
34

Nonsense, I did not pay for the software and I earn money from selling the watchface I design with the free software.

35

Is there any solution to this problem at the moment?
Some pass the screening process, some are rejected. But I don’t know why.

36

A message from Ron @ SDP asking Dev’s to be patient as the WFS are addressing the issue with Google.