Android API 36 (targetSdkVersion 36) support timeline?

Solar2D Android
1

Hello Solar2D team,

First of all, thank you for your continued work on Solar2D.

I have a question regarding Android API 36 (targetSdkVersion 36) support.

The client for my current project has requested that the app be built with targetSdkVersion 36 for Google Play.

At the moment, the latest public Solar2D release appears to support targetSdkVersion 35.

Do you have an estimated timeline for when Solar2D will support building with targetSdkVersion 36?

Even a rough estimate or confirmation that API 36 support is planned would be greatly appreciated.

Thank you!

2

If Android keeps to their schedule from previous years regarding mandatory API targeting, all Play Store submissions will need to target API 36 by August 31, 2026. Last year, there was a build updating to API 35 on June 6, so I expect the update to API 36 will be along soon.

3

Relax, you can tell your client that you can target 36… you can override targetSdkVersion using your gradle file.

4

Solar2D has certainly made its first moves.

3 Likes
5

Hi everyone! we’re in the same situation. We have updated our build.settings to: targetSdkVersion = “36”

However, when building with latest Solar2D Build, the generated APK still reports: compileSdkVersion = 35 and targetSdkVersion = 35

Amazon Kids+ now requires targetSdkVersion 36 for their upcoming Fire Tablets, so we’re currently blocked by this.

Is there any ETA for a Solar2D release (or Build Server update) that supports building with API 36?

Also, @solar_dev, you mentioned that it’s possible to override targetSdkVersion using the Gradle file. Could you explain how to do that when using the Solar2D Build Server? Is there a way to provide a custom Gradle configuration, or were you referring to local/native builds?

Thanks!

6

You can try to create AndroidResources/corona.gradle
with this code:

android.defaultConfig.ndk.abiFilters "armeabi-v7a",  "arm64-v8a"

android {
    compileSdkVersion 36

    defaultConfig {
        minSdkVersion 26
        targetSdkVersion 36
    }
}
1 Like
7

It works! Thank you Kan98!

1 Like
8

Haven’t used it yet but targetting API 36 is possible now with the latest release:

2 Likes
9

Just a quick reminder to anyone who’s feeling stressed about this, you can go into the notification, tap “View Details” and that page has a “Request more time” button. Select “I am waiting on a new SDK version from an SDK provider.” and you will be given an automatic extension to November 1.

There is no need to rush out an update before all the potential plugin conflicts, etc. have been worked out.

2 Likes
10

Is there a key for build.settings that can specify the targetsdk?