Repository navigation
API-34: Support targeting JDK 17 #8304
Description
Activity
Thanks for bringing this to our attention. The first version of Android that supports JDK 17 will be Android 14, which is still in beta.
We made a list of the things we need to do in order to get support for JDK 17 into .NET 8 / API-34 this morning. We are hoping to get that support into .NET 8 RC 2.
Note that if you are still using Classic Xamarin.Android, API-34 will not be supported there, so it likely will not be receiving JDK 17 support.
- changed the title
[-]Can't create .aar binding library that targets JDK 17[/-][+]API-34: Support targeting JDK 17[/+]on Aug 28, 2023 We will also need to update
$(LatestSupportedJavaVersion)to17.99.0as part of JDK-17 support.- added a commit that references this issue
on Aug 29, 2023 Thanks for clarification, guys. I guess this issue can be closed?
We're going to use this issue as our reference for adding JDK 17 support for API-34. 😁
Reacted by Miha Markič and BradThis should be completed for the upcoming releases:
- Classic XA 13.2.2
- .NET 7 7.0.402 (?)
- .NET 8 RC2
- locked and limited conversation to collaborators
on Jan 22, 2024
Android application type
Classic Xamarin.Android (MonoAndroid12.0, etc.)
Affected platform version
VS 2022 17.x
Description
I'm trying to create a binding library for an .aar library that targets JDK 17
I'm getting this error: javac.exe error JAVAC0000: class file has wrong version 61.0, should be 55.0
And there seems no way to use (Open)JDK 17 as VS build really really wants to use 11 even if 17 is installed as well.
Is there any way to use JDK 17? Hopefully official support is planned soon.
Steps to Reproduce
Did you find any workaround?
Use an older version of the library that targets JDK 11.
Relevant log output
No response