android: NET 8.0 LTS doesn't support latest Android SDK 35

Android framework version

net8.0-android

Affected platform version

.NET 8

Description

.NET8.0 was released in November 2023 as an LTS (long-term support) version of .NET. That was implying that all updates will come to this version untill November 2026. But as for now, we see that the latest workloads for net8.0-android doesn’t support Android SDK 35, they have only version 34. Version 35 is available in .NET9.0 (which is short-term support) and .NET10.0 (which is still in preview).

Due to these reasons, I want to clarify, will there be any support for Android SDK 35 (and later 36 when it will be released) added to the .NET8.0 ? Also, maybe you can propose some workarounds (or better to say legitimate approaches) to support the latest SDK and not update to the .NET9-10 for the following year. Any help and advices would be helpful here. As for the updating to the .NET9.0, it’s not quite good solution for our frameworks and projects, since it is not LTS version, and also it might be a bit painful (at least it was so during the update from .NET7.0 to .NET8.0).

Steps to Reproduce

Create .NET8.0 android project, then check the workloads that are added for Android. They will have only version 34, but not 35.

Did you find any workaround?

No response

Relevant log output


About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 5
  • Comments: 22 (13 by maintainers)

Most upvoted comments

There isn’t anything stopping you from targeting API 35 with .NET 8 and your AndroidManifest.xml:

<uses-sdk android:targetSdkVersion="35" /> There is likely a build warning caused by this you can ignore.

The bindings for API 35 are in .NET 9. The general .NET policy (as well as Visual Studio), is to not add new features and APIs in service releases. We would do so if was required by Google Play, however; but I don’t think that is the case here at all.

targetSdkVersion=“35” does not compile an app with Android SDK 35. also, targetSdkVersion can not be higher than compileSdk. with .net8 workloads compileSdk set to 34.

https://medium.com/@iamnajmudheen7311/demystifying-target-sdk-and-compile-sdk-in-android-development-6ec401e79ade

As I described above, it’s not quite good solution for our frameworks and projects, since it is not LTS version (meaning that we will need to make upgrade the process again in a year or even earlier) , and also it might be a bit painful (at least it was so during the update from .NET7.0 to .NET8.0).

I can understand why SDK 36 might not be supported, it was released last month, and it’s quite a tiny room. But the situation with SDK 35 is unclear for me.

It’s like there is an official out of support date for .NET8 (Android workload), but actually its support partially stops even earlier, like more than 6 months prior, probably in August 2024 (that was the release date of the first .NET9.0 preview with SDK 35, which shows that SDK binidngs were at least prepared, but apparently without plans to include it into .NET8.0)

@dellis1972 it still doesn’t explain why there’s no support for SDK 35. According to the Android SDK release notes, stable version of SDK 35 was released in June 2024, moreover, stable version of SDK 36 was released in March 2025.

By this logic with the release cadence of native API, .NET8.0 should support SDK 35, and even SDK 36, since it should be supported till May 14, 2025, even by MAUI support dates (also, it’s quite inconsistent, that there’re different support dates for quite tightened parts of the framework)

Agree, it’s the first time ever I’ve seen that LTS is not real LTS for Android and iOS.

Also, every year we have the trouble in a team, when in September/October someone update macOS or Xcode, and can’t work, because current .net version doesn’t support current iOS version.

And usually you add this support in 2-3 weeks after dozens of complaints. Why it can’t be done in advance? Why I need to wait till mid of November to support latest iOS?

@jonpryor this information is something quite new:

.NET 8 is LTS for console apps, WPF, ASP.NET Core, etc. It is NOT an LTS release for Android or iOS or MAUI. MAUI and the mobile workloads are on the Modern lifecycle, and a release (.NET 8) is only supported for 6 months after a subsequent release (.NET 9).

I can understand that there’re MAUI Modern Lifecycle rules, that you use, where you clearly state that support of .NET8.0 will end at May 2025. However, the comment above is the first time I see that a release (.NET 8) is only supported for 6 months after a subsequent release (.NET 9). Is it stated somewhere, except this comment?

I am asking it because it is quite frustrating to work with a .NET framework and its workloads without clear picture about support. With .NET8.0 there was a hope for LTS release, which was a bit diminished with Modern Lifecycle (but still, it declared quite long support). But this comment about only 6 months after subsequent release literally destroys the meaning of LTS releases in mobile development for .NET.

You also mentioned, that:

There are no LTS releases of the mobile workloads.

Does it mean that in mobile development for .NET, there is no meaning for LTS versions, and as a result, we should just update the framework each year (or what other time span will take for a new major version of .NET to be released), without taking into account if it’s LTS or non-LTS version?

@Saratsin asked:

it still doesn’t explain why there’s no support for SDK 35. According to the Android SDK release notes, stable version of SDK 35 was released in June 2024, moreover, stable version of SDK 36 was released in March 2025.

Your timelines don’t take into consideration how much time it takes us to bind a new SDK and to release the binding.

Yes, API-35 was released in 2024-June. We did not ship bindings for API-35 until 2024-November, with .NET 9. .NET 8 did not get bindings for API-35 because it’s extra work that (effectively) “nobody” has requested.

Yes, API-36 was released in 2024-March. Android 16 does not yet exist in any non-preview capacity. We are not yet shipping any stable bindings for API-36 at this point in time, and are unlikely to do so outside of .NET 10 previews before this summer.