Thank you. Been looking for this since june.
Anythig changed about that case of memory usage ? Do you updating your watch faces without problem, or it still actual ?
To me would be interesting to learn, why is every built package bloated with the same additional data? When I only added two images and one font together about 350kB, why there has to be another 650 files (compressed to about 6MB) in 6390 folders (added by wfs 1.3)? It only wastes server and network resources for uploading, downloading, storing the same data in every built watch face, just because this new OS is not capable of holding its own common version of these data. In the .tpk packages for Tizen there were only my added resources and .xml code, but no bloatware at all.
1 Like
The Watch Face team is actively communicating with the Play Console team. Watch Faces are different app type than the normal Wear app and as I understand it the requirements cause the bloat.
Ron
Samsung Developer Relations
Google Play Console warns that if all updates are not completed by August 31, the app will be deleted.
However, the update is currently being rejected due to memory problems. Please discuss with Google about extending the update period.
WFS 1.3.13 generates API level 30 and complies with the requirements.
We are hoping to get a resolution on the memory size for API level 33.
Ron
Samsung Developer Relations
Watchface built with WFS 1.3.13 does not work perfectly with Watch6. So it can’t be a solution. And the face that has already been opened in WFS 1.4.20 will not be opened in the following version.
We need a new WFS that solved the problem quickly. If not, please negotiate the update period with Google.
Samsung will exert more power than individual producers.
1 Like
Hello, from where did you get this info? Why it would it not be possible to open WFS 1.4.20 project with newer WFS version? It does not make any sense since WFS 1.4.20 is currently only version available for download.
That is what I mean. If they are so special, then they had to have them integrated as such and not impose silly requirements. But that is my critique to the OS as is (and that it was accepted as lame it was), not the WFS.
1 Like
I’m sorry. There’s a typo. It means that it will not open from the previous version.
1 Like
I am currently updating my watch faces for the new watchface format with WFS 1.4.20. I have no problems with exceeds memory usage … crossing fingers. But I get a warning message before submitting …
warning
This Bundle app contains native code and you have not uploaded any symbols to debug. We recommend that you upload a symbol file so that your crashes and rabbits can be better analyzed and adjusted by errors. Further information.
Is that important and a problem?
Not unless you are uploading an Android app, if you are uploading a Bundled Android app like many watch face sellers that is what they are warning about.
Ron
Samsung Developer Relations
Do you use images instead of a font for displaying the time, battery status data or other information?
Hi everyone, Tough to quit but something is pushing me back, have made two same watch faces, one with WFS 1.3.13 and the other one with WFS 1.4.20 installed both to my Galaxy watch4, one made with WFS 1.3.13 works perfectly smooth, the other one made with WFS 1.4.20 struggling to work on watch even freeze screen sometime and draining battery in a half an hour, thinking that is not problem with Google play store, they really exceeding memory usage, made some video but is difficult to record perfect, First one is made with WFS 1.3.13
The second is made with WFS 1.4.20
5 Likes
Thank you for taking all The Trouble to make the videos . I am not going to 1.4.20 . There are so many not using it . Everone I know who is making is using 1.3.13 .
I am fine to use 1.3.13 but will watch faces still work after 31 August? as new requirement for API level 30 starting
Yes, they will still work because WFS 1.3.13 compiles the .AAB file with Target SDK 30.
However, if we get any updates regarding this issue, it would be great…
1 Like
Then Samsung needs to solve this thing with a newer version.
Cuz, it’s probably one of the reasons for our problems with Google.
Soon we’ll have problems while publishing our apps in Google Play because it’ll not support watchfaces with API28+ anymore…
First Samsung is in discussion with Google about the memory issue but this must be Googles decision.
Google will still support API 30 and WFS 1.3.13 supports that. However API 33. Now that Samsung Galaxy Watch6 is out and getting more exposure it should be easier to find and fix things that weren’t so evident with the smaller beta tester users.
Ron
Samsung Developer Relations
1 Like