Status Update
No update yet.
Comments
ju...@google.com
je...@google.com
vm...@google.com
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
re...@gmail.com
I'm working for the support team of Unity engine in China.
The android project is exported by Unity. And the developers in China are most using Unity 2022.3.
The gradle version will be 7.x.x which is not compatible with the built-in JDK 21-jbr of latest Android Studio.
The 7.x.x is using Java 11 metioned in our doc. And they won't update to Gradle 8 to keep the best compatibility.
So the developers have to download Java 11 from Temurin as the doc mentioned.
Some people may click the auto detected JDK several times by mistake.
And a lot of JDK is added with the same path.
It's really frustrated.
I think, at least a separate panel in Gradle settings to manage JDKs.
And also, a mechanism that prevent developers add JDKs with the same path by clicking the auto detected JDKs will be great.
Thank you.
P.S. the developers mentioned above are most Unity source code customers. They have the requirement to debug Unity engine in Android Studio.
vm...@google.com
I completely understand your scenario that's why
Unfortunately, in order to take advantage of all of those improvements you need to use a more version of Unity that support recent version of Gradle. While the existing Gradle settings will still be supported for old project. I don't think there's any reason of improving it given that a new and more robust solution will soon be the default for new projects and existing ones will be recommended to migrate.
re...@gmail.com
The only thing they can update is Android Studio.
According to your description. the feature is bond to Gradle 8.8. Right?
So it has to be solved without gradle 8.8.
vm...@google.com
This is something that can be reconsidered if issue gets more interest but at least for now our direction is clear on suggestion project of using Daemon toolchain. We already spend huge effort on tackling those issues for the root so at least isn't something critical will be difficult to be considered as higher priority when there are workarounds in place.
Description
Some times sdk will be added duplicated. But I can't find a way to remove it except modification of jdk.table.xml directly in the Android Studio data folder.
STEPS TO REPRODUCE:
1. Setting
2. Build, Execution, Deployment
3. Build Tools
4. Gradle
5. Gradle JDK: add an SDK by mistake
6. You can't delete it without modification of jdk.table.xml directly in the Android Studio data folder.
ATTACH SCREENSHOTS/RECORDINGS OF THE ISSUE
Screenshot 1 is Android Studio. You can't delete it without modification of jdk.table.xml directly in the Android Studio data folder.
Screenshot 2 is IntelliJ IDEA. You can simply remove the JDK.
ATTACH LOG FILES (Select Help > Show Log in Files, or Show Log in Finder on a Mac)
No related
------------------
IMPORTANT: Please read
all required information.
------------------
Studio Build:
Version of Gradle Plugin:
Version of Gradle:
Version of Java:
OS: