Support for Android 16 (API Level 36) in Mendix 10.24.6

0
Hi Mendix Team,I am currently using Mendix Studio Pro 10.24.6 to build a native mobile application.After uploading a new Android App Bundle (AAB) to the Google Play Console, I received the following policy warning:"App must target Android 16 (API level 36) or higher."The Play Console indicates that my application is currently targeting Android 15 (API level 35) and that, after August 31, 2026, app updates must target Android 16 (API level 36). I would like to know:Does Mendix 10.24.6 support targeting Android 16 (API level 36)?If not, is support planned in an upcoming 10.24.x patch release or a newer Studio Pro version?Will updating the Native Mobile Resources/Native Template be sufficient, or will a Studio Pro upgrade also be required?Is there any official documentation or migration guide for updating Mendix native apps to target API 36?Any guidance would be appreciated.Thank you!
asked
2 answers
0

Hi Krushna,

As far as I know, targeting a newer Android API level is mainly handled in the Native Template rather than Studio Pro itself.


If you're using the latest Native Template/Native Builder, you should be able to:

  • Open the Android project in Android Studio.
  • Update the Target SDK to API 36.
  • Sync the Gradle project.
  • Build a new AAB and upload it to the Play Console.


If you're on an older Native Template, you may first need to update it to the latest version before changing the target SDK.


Kindly mark this as the accepted answer if it helps.


answered
1

Just wanting to let you know I have made a Ticket with Mendix Support on July 28th for this same exact issue, and their response was:


"We checked this with our R&D team and they already have started working on the implementation to support API Level 36.

We will keep you posted as soon as we have more information. For now, I will place your ticket on Hold and update you once the fix is released in coming weeks."


I am assuming they will come out with a new Native Template version, as Krishnakumar mentioned, which we then need to implement and build with.


In the meantime, it's possible to ask Google for an extension period (until november 1st), as you are essentially waiting for a vendor to fix the issue.

answered