Fixed
Status Update
No update yet.
Comments
ne...@soundcloud.com
I understand it is fixed in the canary, but what about the stable version of Android Studio? Should we expect broken features to be fixed in stable versions?
uc...@google.com
xa...@google.com
sr...@google.com
As mentioned before, this issue has been fixed on 3.6 and now the fix is also applied on the 3.5 branch. Unfortunately the fix is not part of 3.5.1 but if a new 3.5 release is done (probably 3.5.2) this issue will be fixed on it as well.
Description
Seems like this is pretty similar to this other issue, but this is broken in the stable version of Android Studio 3.5.0.
I added the following to my build.gradle to ensure that Gradle could actually find my JAVA_HOME and it does.
```
println(System.env.'JAVA_HOME')
println(System.getProperty("java.home"))
```
Output:
```
/Library/Java/JavaVirtualMachines/jdk1.8.0_181.jdk/Contents/Home
/Users/no/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-1/191.5791312/Android Studio.app/Contents/jre/jdk/Contents/Home/jre
```
Also my JAVA_HOME is properly set in the terminal:
echo $JAVA_HOME
/Library/Java/JavaVirtualMachines/jdk1.8.0_181.jdk/Contents/Home
If I manually set the JDK location to /Library/Java/JavaVirtualMachines/jdk1.8.0_181.jdk/Contents/Home, then I get the following warning:
To use the same Gradle daemon between Android Studio and the command line, select JAVA_HOME from the drop-down.