Android Studio doesn't respect the STUDIO_GRADLE_JDK environment variable [213266836]

Fixed

Bug

Status Update

No update yet.

Description

lo...@gmail.com

created issue #1

Jan 6, 2022 09:34AM

Hello,

I upgraded Android Studio from BumbleBee beta 5 to RC1, and I got greeted by the following message in the "Event Log" tool window (you can also check the attached screenshot):

Project SomeCompanyProject is using the following JDK location when running Gradle:

/Users/me/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-3/211.7628.21.2111.8005941/Android Studio Preview.app/Contents/jre/Contents/Home

Using different JDK locations on different processes might cause Gradle to spawn multiple daemons, for example, by executing Gradle tasks from a terminal while using Android Studio.

More info...

Select a JDK

Do not show this warning again

This is not right because I have the STUDIO_GRADLE_JDK, which I left unchanged and it was correctly used by Android Studio on BumbleBee beta 5.

I don't know if the unwanted Gradle JDK change is linked to some code running on upgrade, or some regression specifically introduced in RC1.

Can you explain a bit what happened, and if there are any ways to prevent Android Studio from doing these unwanted config changes?

IDE info

Build: AI-211.7628.21.2111.8005941, 202112152349, 

AI-211.7628.21.2111.8005941, JRE 11.0.11+0-b60-7590822x64 JetBrains s.r.o., OS Mac OS X(x86_64) v11.6.1, screens 2880.0x1800.0, 5120.0x2880.0; Retina

AS: Bumblebee | 2021.1.1 RC 1; Kotlin plugin: 211-1.6.10-release-923-AS7442.40; Android Gradle Plugin: 7.1.0-rc01; Gradle: 7.3.3; Gradle JDK: Azul Zulu Community™ version 17.0.1; NDK: from local.properties: (not specified), latest from SDK: (not found); LLDB: pinned revision 3.1 not found, latest from SDK: (package not found); CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)Source: user_sentiment_feedback

Thank you and have a great day!

Louis CAD

Screenshot 2022-01-06 at 10.33.50.png

135 KB

View

Download

Comments

ps...@google.com <ps...@google.com> #2Jan 6, 2022 03:03PM

Thanks for the feedback. To help us troubleshoot this issue further, we will need more information. Please share detailed reproduction steps and as much as possible of the following information when it applies:

1. Gradle and Android Plugin Version (File -> Project Structure -> Project)
2. Build logs
3. idea.log file if the issue occurs from Android Studio (select Help > Show Log in Finder / Explorer)
4. Gradle profile if it is a performance issue as described in

https://developer.android.com/studio/build/optimize-your-build#profile

For more information on what’s needed and how to obtain this information please read the guide at

https://developer.android.com/studio/report-bugs#build-bugs

lo...@gmail.com <lo...@gmail.com> #3Jan 6, 2022 03:47PM

I already provided the reproduction steps. Do you have any real blocker to start analyzing this issue?

pa...@google.com <pa...@google.com> Jan 7, 2022 04:39PM

Assigned to an...@google.com.

ju...@google.com <ju...@google.com> Jan 14, 2022 01:21AM

Status: New

vm...@google.com <vm...@google.com> #4Mar 9, 2023 01:49PM

Marked as fixed, reassigned to vm...@google.com.

First of all, we improved this message due to the following issue: https://issuetracker.google.com/issues/237043557 displaying now also your JAVA_HOME path. Unfortunately in your case, we don't have the JAVA_HOME to be able to compare, but in any case, there are different things to consider. When defining the STUDIO_GRADLE_JDK environment variable, if valid (important otherwise will be ignored) this will be used to configure the Gradle daemon for the project sync. To confirm this selection, you can open the Gradle settings and the selected Gradle JDK should be STUDIO_GRADLE_JDK. However, you still have the option to move away from it by selecting a different JDK from the dropdown, but this selection isn't persisted.

Definitely in your case, the defined STUDIO_GRADLE_JDK environment variable is completely ignored in the AS (supposing that is valid), a scenario that I was able to reproduce it on my end, figuring out an issue about obtaining the system environment variables. You probably have defined the STUDIO_GRADLE_JDK under ~/.zshrc and most probably if you ran the AS from the command line then the variable will be resolved properly. This is a synchronisation issue regarding the command line and GUI applications. A fix will be added on AS G Canary 10 that will address this by taking into consideration the shellScript environment variables simplifying this and keeping alignment with android docs. Please feel free to test with the mentioned version and let us know if this was your case.

As a note, any change regarding your STUDIO_GRADLE_JDK requires restarting the AS to apply those changes. Another workaround will be to use the Gradle property org.gradle.java.home defined under your GRADLE_USER_HOME or Gradle installation directory allowing to have a unique source of truth regarding your Gradle JDK selection between different projects.

Message last modified on Mar 9, 2023 01:50PM

gradle settings.png

116 KB