Hi Tomas,
Shortcuts
TAGS
Bitmaps
10 elements @ 450x450 for battery bar
Maybe try this:
This way maybe you’ll be able to find out what’s exactly causing the memory issue.
It’s time consuming, I know.
I only had this issue with one release and it went through after I submitted another build.
Tomas
Hi @ALITHIR if you downgrade the WFS version, the API will be less. Apps with a target level of Android 11 (API level 30)* or lower will not be available to new users running the Android OS higher than apps’ target API after August 31, 2023.
Hi @ALITHIR alit how many theme color palette used for this
Wrong.
don’t know I am right or wrong. But i got it from below google link - which is right.
Thing is watch face rejected from many designer and i am trying to find it out. Also note, i have submitted a new watch face just an hour back and it is approved.
Watchfaces made in v1.4 can be approved, but (no offense) they have to be quite minimal and not so much customizable. Regarding the API level, @amoledwatchfaces is right. We can safely use v1.3 at the moment, the api requirements are different for WearOS specific apps.
nice to hear that. 
Yep, Google Policies requiere a minimum (not minSDK) of 30 for targetSDK (Wear OS)
If I’m not wrong, Galaxy Watch 4 and later watches were released with Wear OS 3 (3.5) - API 30
First WFS was released with targetSDK of 30? (I think it was)
So basically all watch faces created with any version of WFS will work on Wear OS 3, 3.5, 4.0 (may not work so good).
Currently, existing apps (across mobile, Android Auto, Android TV) must target API level 31 or above by August 31st, 2023 (target API 30 for Wear OS)
About minSDK. WFS 1.3.13 and older version have minSDK set to 28+. WFS 14.13 and later have minSDK set to 30+. This means that watch faces created with newer WFS versions (1.4.*) will stop working on older smart watches with Wear OS 2
We hope to receive detailed information about this issue soon and, of course, how to fix it.
It would be extremely stressful to try and try, especially for old watch faces that will need to be updated sooner or later.
Very true. A beginer like me have about 150 apps to update. Imagine seasoned developers, must be in thousands. August 31st is the deadline.
I received the same app rejection today. This was my first watch face created with the new version of WFS. The watch face includes three complications and a 90KB animation. I optimized the PNG files and submitted them for the second time, but received the same result.
I’ll let everyone know if there is any update.
When you read the guide don’t get stuck just on the memory issue if you go further down there are a lot of other stuff about icons and what must and must not be in app descriptions that is new.
Ron
Samsung Developer Relations
Another try, this time i updated a watch face with the new 1.4.20 version (just added 3 more color combinations to a simple analog watch face). It was rejected. Reason: “Watch face exceeds memory usage”. I then made the same update with the 1.3.13 version and it was accepted.
Hi Bobota, did your app pass review after deleting the ReTrace thing?
Both my rejected apps built with WFS1.4.20 does not have that file.
Thanks.
I believe the issue at hand is not simply about the size of the AAB file, but rather the RAM occupancy. A monitoring system for tracking the RAM usage required to run the watch face is needed.
Hey, I have the same issue and i’m trying to find a link to get the 1.3 version but cant find any. Can anyone help me downgrade?
how can i go back to 1.3?
Courtesy of Peter 1.3.13
