One of our native mobile apps is currently published using a MABS 10.0 build (which is deprecated). Google Play recently sent the following notification about the app:
"To ensure that your app works correctly on the latest versions of Android, Google Play requires all apps targeting Android 15+ to support 16 KB memory page sizes. From 1 May 2026, if your app updates do not support 16 KB memory page sizes, you won't be able to release these updates."
I've read Google's documentation on 16 KB page sizes but I'm unsure how to implement it on OutSystems. The release notes for MABS 11.0 and MABS 11.1 don't mention anything about page sizes.
We've already got a backlog task to upgrade the app to MABS 11.1. Will this also fix the page size issue, or is there something else we need to do?
Hey there, MABS 11.1 and official plugins all support 16KB page sizes. For official plugins, make sure you use the latest versions.
If you'd like to check if the app generated with MABS 11.1 is 16KB page size compatible, you could upload your app to Google Play and it will analyse for any page size incompatibilities, and where they come from. Alternatively, you can also use the APK Analyzer tool in Android Studio - https://developer.android.com/guide/practices/page-sizes#identify-native-code -, or do it via terminal - https://developer.android.com/guide/practices/page-sizes#elf-alignment. You may also test your app in a 16KB page size device, but this is limited to emulators and latest Pixel devices.
Any app using MABS 11.1 only official plugins in their latest version, should already be supporting 16KB page size devices.
If you find incompatibilities, and you are using MABS 11 and latest versions of official plugins, it could be you are using an unofficial plugin that hasn't been made compatible yet. Most mobile plugins are compatible out of the box, but if they have some compiled C++ code with NDK, they most likely would need to be recompiled by the plugin developers. The aforementioned tools will mention which shared library (.so) file is causing the problem, and depending on the name of the file, it may or may not be obvious which plugin is the culprit. If you are unsure, you may try cloning the plugin and see if their source code mentions the library, or ask OutSystems support to help you identify. The next steps would be either to contact the plugin developer to ask to update the plugin, stop using it, or clone it and make the necessary adjustments.
Hope this helps!
Hello @Ross Jennings ,
MABS 11.1 does not explicitly mention support for 16 KB memory page sizes in its release notes. However, since Google Play mandates this for apps targeting Android 15+, it's crucial to ensure your app complies.
Here's what you should consider:
MABS 10.0 is deprecated, so upgrading to MABS 11.1 is a good step toward future compatibility and support.
OutSystems has not officially confirmed whether MABS 11.1 supports 16 KB page sizes. This means:
You should reach out to OutSystems support or check their latest documentation and forums for updates.
Alternatively, monitor the OutSystems release notes for upcoming MABS versions (e.g., MABS 12) that may explicitly address this requirement.
Warm Regards,
Vibhor Agarwal