cargo-apk doesn't support Android Platform 36.1

[rvandermeulen]

Google recently released Android platform 36.1 tied to the upcoming Android 16 QPR2 release, installed in the expected $ANDROID_SDK_ROOT/platforms/android-36.1 location.

Unfortunately, cargo-apk doesn't seem to recognize non-integer android-XX values, so builds end up failing with "Error: Android SDK has no platforms installed." instead.

I don't know how commonplace this is going to become in the future, but I suspect it will be as they've also changed their Gradle DSL to accommodate minor API levels now as well.
https://developer.android.com/reference/tools/gradle-api/8.13/com/android/build/api/dsl/CompileSdkSpec

[MarijnS95]

The only place where we use the parsed platform paths is to guess what the highest supportable target SDK is together with what the NDK supports:

cargo-apk/ndk-build/src/ndk.rs

Lines 201 to 203 in 887423a

	pub fn highest_supported_platform(&self) -> u32 {
	self.platforms().iter().max().cloned().unwrap()
	}

Separately we piece together the android-{level} directory back based on that highest number or whicheve the user ended up specifying in their crate metadata:

cargo-apk/ndk-build/src/ndk.rs

Lines 213 to 217 in 887423a

	pub fn platform_dir(&self, platform: u32) -> Result<PathBuf, NdkError> {
	let dir = self
	.sdk_path
	.join("platforms")
	.join(format!("android-{platform}"));

The constructors for that DSL are pretty unclear, as they seem to suggest that ext only exists for a released version (all numbers) but I see a preview installation as well in sdkmanager:

android-35/
android-35-ext14/
android-36/
android-36.1/
android-36-ext18/
android-36-ext19/
android-Baklava-ext19/

Additionally there is no way to target or distinguish a major SDK in the API level of an app, which will require some refactors in cargo-apk to handle appropriately:

https://developer.android.com/guide/topics/manifest/uses-sdk-element

Despite its name, this element is used to specify the API level, not the version number of the software development kit (SDK) or Android platform. The API level is always a single integer. You can't derive the API level from its associated Android version number. For example, it isn't the same as the major version or the sum of the major and minor versions.

Can you install SDK 36 for the time being until this is released stably and I can think of a better way to handle it?

[rvandermeulen]

Yeah, it's not a problem doing that for now. My bigger worry was that this is going to become more commonplace going forward.

[rvandermeulen]

The other issue we encounter in our CI relates back to #62 where even the latest NDK r29 only says 35 is the max supported version, tripping up that check. We've had to resort to forking around the issue. I wonder if utilizing the target_sdk_version from package.metadata.android.sdk would make sense as an alternative way of specifying which platform version to use?