SAP Asset Manager apk size limitations for upload to Play Store

[gonzalo_reyna]

Hi everyone,

I have noticed the following:

- The current SSAM Client in Play store size is under 100 MB.

- Previous versions of SAM Client (before being SSAM), if I am not wrong, had sizes around 300MB.

We are creating the android .apk for a client that has SAM 2010 and wants to upload the application to the Play Store. The generated .apk via sap sdk is around 300MB. However, there is a max. size limit of 100MB in the Play Store.

Any recomendation of how can we overcome this issue?

Best regards,
Gonzalo.

[robinkuck]

Hi Gonzalo,

in addition to the information provided by Muhammad you can perform the following steps to reduce the size:

1. Edit the AndroidManifest.xml file and set the parameter android:extractNativeLibs to true
2. Remove MDK extensions you don't use
3. Edit the app.gradle file to remove architectures from abi filters (for example x86 and x86_64). Alternatively, build 1 apk per architecture

[andreas_gall2]

Hi kucki99,

your first and third hint did the trick. With these two tweaks I could reduce the inital apk size of over 400 MB down to 87 MB.

[michaelhaydock]

This can be addressed by creating a bundle (AAB file) instead of an APK file. Just add "--aab" onto the end of your "tns build" command. This is Google's preferred app format now.

[andreas_gall2]

But without some tweaks described kucki99 event aab files are too large. In my scenario (SAM 2210) the initial apk file was over 400 MB and the aab file over 190 MB. Googles cap is 100 MB for apk and 150 MB for aab.

[michaelhaydock]

I think the 150MB limit is for the APK generated from the AAB for any one device that downloads the app. The Play Console will calculate this on AAB upload. The AAB you upload can be larger than 150MB. All my SSAM uploads in AAB format are larger than 150MB and I can confirm it works fine.

[andreas_gall2]

I remember that builds done with the KapselSDK created several APKs for each architecture: x86, x86_64 and arm. And Kapsel by far isn't exactly state-of-the-art. Maybe this "feature" can be implemented in the MDK build process instead too?

[gonzalo_reyna]

Thank you Muhammad and Robin for your quick response.

Yes the existing app is less than 100MB. I meant previous standard clients (like SAM 2010), if I am not wrong, were bigger.

However, I will check and try what you have indicated in both comments and will comment back here I any of those solve the issue.

[muhammad_rafay]

The existing app in the play store is less than 100MB. Following links might help

https://developer.android.com/topic/performance/reduce-apk-size

https://developer.android.com/ndk/guides/abis