Java 9 (JDK 9) support by Unity Android

I think that it could be made clearer by adjusting the wording and perhaps add a "common mistake" paragraph regarding android sdk's current Java constraint.

Unity itself is more than happy to accept the Java 9 and 10 path and when building the only error I got was "Unable to list target platforms", which wasn't particularly helpful for troubleshooting. Also, the android sdk seems to use by default the highest installed Java version. So setting the Java path in Unity didn't seem to do anything.

 

Depending on how long it will take to get that JDK constraint removed, I would add that recommendation right next to the JDK install instruction e.g. like that for immediate visibility when following the install guide (https://docs.unity3d.com/2018.2/Documentation/Manual/android-sdksetup.html):

1. Install the Java Development Kit
Download and install the Java Development Kit (JDK). Unity requires the 64-bit version JDK 8 (1.8).
Note: Currently due to software incompatibility, we recommend to uninstall latest JDK and to install JDK8 only.

 

Hello - I have followed the main instructions as well as what has been suggested here.

I'm using 172 instead of 152 for JDK.

This is what I'm getting for an Error:
CommandInvokationFailure: Unable to list target platforms. Please make sure the android sdk path is correct. C:/Users/*******/AppData/Local/Android/Sdk\tools\bin\avdmanager.bat list target -c

I have tried to follow all of the instructions I can find with fixing my PATH variable - but perhaps I'm missing something?

 

At the moment, that seems to be fixed if you download the older version of the Android tools. Not sure why the docs aren't updated to show this...

Replace your tools folder with the folder in this package:

http://dl-ssl.google.com/android/repository/tools_r25.2.5-windows.zip

I still can't get Unity to find a 'compatible device' even with all of the other bits and pieces set up (A whole mess of different SDK versions (including the one that my device has!), build-tools 27.0.3 and the google USB driver - adb detects it, and it's in the Unity build settings). It's really frustrating how light the docs are. Perhaps the device specific drivers are too new...

So many other locations for answers, and no-one is updating the docs to show that there clearly is a need for a 'troubleshooting' section.

**Edit: Oh, hey! there is a troubleshooting section. Alas, it's already telling me things that I have done, and they don't work..

**Edit 2: As an aside, I am able to export the project instead and open it in Android Studio and deploy it from there. It told me what the error was - in Player Settings, I had not ticked the ARMv7 box. Which is obvious when you see it! It would be really good to have the Unity Process updated to give a more detailed error.

 

I've tried everything... I have the last unity version, I've tried jdk10,jdk9 and jdk8, I've downloaded android studio.. so I think to have the last android-sdk version(?!?!?)

Now has you say I uninstalled all the jdk versions exept for jdk8... but nothing... I can't build the app because of this: unity unable to list target platforms ... etc. etc.

Please help me... I lost all the day trying to fix it.
I'm going to format the **** pc.....

 

I'm having the same "Unable to list target platforms" problem when trying to build for Android.

I'm using:
Unity 2018.1.2f1
The latest tools for the Android SDK
jdk 1.8.0_121 (the only JDK installed on my computer)

And I'm still getting this error. Is there any solution available?

 

Everything is installed/updated (except JDK 8) and I'm still getting the errors. This is driving me absolutely insane.

 

I managed to get it to work. I had to replace the tools files with an older version. The first time i tried it didn't work because i was using the newer jdk, but once implemented the fixes in this thread and than tried to tool method it worked.

 

You keep saying that and yet here we are.

 

My solution was uninstalling Java 10 and reinstalling Java 8 on Windows10.

 

It would be really great if Unity could update the Android Environment Setup document in the manual to reflect that the latest jdk doesn't work with the latest versions. Wasted many hours on this relatively simple fix.

 

If you're using Android Studio, doesn't it default to using the internal Android Studio JDK anyway? I went into the studio and changed the JDK from the internal JDK to the Java 8 JDK (https://www.jetbrains.com/help/idea/configuring-mobile-java-sdk.html) and there's no other JDK's on my system, but I'm still getting the "Unable to list target platforms" error.



I'm not sure what I'm doing wrong, I've read through this whole forum thread and I can't find anything that's worked.

This is 2018.2 with the most recent android studio and the Java SDK 8

 

Hi,

I just upgraded to 2017.4.10f1 and before this version I could build and sign my android app without any problems.

Now I can sign it to release mode, but I can't build in debug (unsigned).
I get the error 'CommandInvokationFailure: Failed to sign APK package.'

Any idea what is causing this? It has to be Unity, as I changed nothing else other than upgrading Unity from 9f1.

Thanks.

Edit: I just downgraded to 9f1 as I don't have time to mess around with this - everything is building / working as it should again.

 

export JAVA_HOME=$(/usr/libexec/java_home -v 1.8)

open -n /Applications/Unity/Unity.app

https://github.com/RWebRTC/Blog/issues/37

 

@Yury-Habets - when can we expect 2018.3?

I cant seem to get any working Android builds with 2017.X and in 2018.1-2, for some strange reason, if I try to change from Gradle to Internal, it completely crashes the editor. Reopening unity does nothing. It just automatically crashes my editor until I open a different copy of my game. Same thing happened when I selected export project. Tried submitting a report and even that wouldnt go through. Tried everything I've found on google and the forum to no avail.

Tried downgrading to 2017.4.12 and it picks and chooses which errors it wants to give me to ruin my day. If I select internal, it'll say my manifests cant merge (despite everything being correct), if I select Gradle, it'll give me the JDK issues, and it'll throw in Google.JarResolver.ResolutionException: Cannot find candidate artifact for, and UnityEditor.BuildPlayerWindow+BuildMethodException: 4 errors.

 

Does this mean I can remove Android Studio now? I have no other need for it outside of Unity.

 

After installing 2018.3 I have run into a problem that seems to be related to this. All my Java scripts worked before, now they're not recognised. I'm installing Java separately to see if it gets it working...

 

Hi, I facing this issue
"Your app bundle contains the following configurations where the initial install would exceed the maximum size of 100 MB: ARMEABI_V7A"
If I upload app bundle under 100mb size then work fine. How I upload app bundle with more then 100mb size.

 

@Yury-Habets
Any chance you could bundle the latest SDK tools, platform-tools, build-tools with the Android Support Installer?
These are way trickier than simple OpenJDK configuration.

 

@Yury-Habets That's awesome, but the SDK Tools are bundled together with the NDK Tools.
Would be far better if the SDK tools are part of the Android Support and the NDK remains optional.

 

This is also an issue with JDK 11 as well (I had to remove it to get my project to build)

I realise this may have been fixed with a newer version of Unity - I'm still on an old version for my project but plan to update soon.

 

@JC-Cimetiere I understand, but may I argue that if the motive behind this move is avoiding conflict and simplifying the process then I think it's even more suitable to include the SDK, because with the same rationale, you can't build an app with the JDK alone, it's pretty useless on its own, but it's way easier to set up then setting up the SDK.

The OpenJDK version that ships with Unity happens to be the same I've been using in my PC for the last 1.5 years (1.8.0_152), same with the NDK (16b), ...on the other hand Unity is already complaining about a deprecated SDK tools and platform tools and I'm still trying to update them.

So for me at least, It seems obvious to me that setting up JDK and NDK is least troublesome, the more stable part, so I don't understand why I have to keep reinstalling them with each Unity minor version.
Whereas the SDK is the more volatile and troublesome setup. especially if you're using it without Android Studio, and unfortunately there's no longer a GUI installer or GUI SDK manager provided by Google.

It's my opinion but I would prefer a bundled SDK instead of Java, and in any case I would like to propose that the Andoid Installer per se gives the option to untick all the extra dependencies so as to not reinstall them if the same version is already installed.
I'm not sure if the Nullsoft installer used by Unity supports it or not but it's worth a try.

 

@JC-Cimetiere To maybe illustrate the point, after leaving Unity update the SDK toolchain overnight, yes overnight, I wake up to see it failed .

There is this weird conflict and I have to update it manually after all.
Here is a screenshot if you're interested.

From the looks of it, Unity spent the night downloading the emulator which I don't need, and I'm not even sure which packages need updating and to what version.

My sdk directory became a hot mess and I'm neck deep trying to figure it out in the command line and stackoverflow, I would take a simple Java mismatch over this any day.

 

Hi Yury-Habets, this is a great feature. I'm having issues using a headless build (Jenkins) where I can no longer set JAVA_HOME to use JDK 8 set up externally. Using Unity 2018.3.10f1.

I am able to get an Android build to complete successfully using BuildPipeline static method call from batch script when signed in as a user who has configured the Android Editor Prefs (SDK, NDK, JDK 8). However, calling this same method from a headless build system fails since these variables are not set. %ANDROID_HOME% and %ANDROID_NDK_HOME% are successfully used when configured however %JAVA_HOME% seems to be ignored. It keeps defaulting to the embedded OpenJDK which is causing build failure (JDK 8 dependency).

I have tried

Code (CSharp):

1.                     EditorPrefs.SetString("JdkPath", @path);
2.                     EditorPrefs.SetInt("JdkUseEmbbeded", 0);
3.                     Debug.Log("JAVA_HOME is" + Environment.GetEnvironmentVariable("JAVA_HOME") + ". About to set to " + path);
4.                     Environment.SetEnvironmentVariable("JAVA_HOME", path);

However, setting these prefs via code seems to do nothing. The environment variable JAVA_HOME is set correctly to an external JDK so overwriting it before calling the build script does not seem to help.

I have inspected UnityEditor.dll with ILspy and can't seem to find anything useful to manually set the JDK path.

 

Thanks for your response.

Currently the Facebook SDK for mobile login/analytics needs JDK 8. I will try your change when I get a chance, but I'm not sure if that will make a difference. Firstly AFAICT the pref was saved as an int in registry and more importantly none of those prefs seem to work if you are signed in as System. I confirmed the same SetPrefs DO work when executing the same command line from a user.

When are these prefs loaded? Can they be dynamically changed right before a build, or does it require restarting Unity? I think this might be related to why it doesn't work -> Jenkins may not keep register/editor prefs between executions.

For now I'm just running Jenkins as a user instead of System (though I think this may cause other issues and unfortunately requires one time setup per build machine).

 

Hi guys. So can use newer JDK now or still stick with JDK8?

 

Hi @Yury-Habets,

I have a problem that is forcing me to use download Android Studio and preventing use of these new embedded features.

I've transferred my project to another PC to do PC housekeeping on the main machine. The backup PC doesn't have Android studio or any Android tools on other than those that installed with unity (that is the embedded ones). I don't want to add Android studio etc to the backup PC as I'm trying to do things the new unity way. Plus hopefully keeping the PC tidier.

I've installed a fresh unity 2018.4.1f1 with all the android components and selected use embedded JDK and NDK in the preferences.

The build always fails and says 'Unable to locate Android SDK'

I've checked the Android components have installed via Unity hub and it shows they are installed. Does the Android component actually include the SDK? I would assume if unity is making use of an embedded component that it would download/include all the SDK's etc needed? It does say so in the tick box when downloading unity and the android component.

Is this a bug?

Either way is it possible to just explicitly set the Paths to the embedded components? If so where are they?

Thanks

 

Hi @JuliusM,

Thanks for the reply and clearing this up.that explains why I couldn't get it working until installed Android Studio.
Not sure if you've made a notice of this but would be good to let people know especially with 2018 being an LTS now.

I was going to use 2019.1 but there's a weird bug with UI sprites changing size for no apparent reason.

Thanks anyway.

 

Hello,

I have an issue with this setup using Unity 2018.4.2f1 where I have the external tools set to use the embedded JDK. I specify the SDK and NDK locations to match the current Android Studio setup. However, when I try to run the Play Services Android Resolver, I get the following error:

Code (CSharp):

1. Gradle failed to fetch dependencies.
2.  
3. Failed to run 'C:\BitBucket\RubyRei_Android\Temp\PlayServicesResolverGradle\gradlew.bat -b "C:\BitBucket\RubyRei_Android\Temp\PlayServicesResolverGradle\PlayServicesResolver.scripts.download_artifacts.gradle" --no-daemon "-PANDROID_HOME=C:/Android/SDK" "-PTARGET_DIR=C:\BitBucket\RubyRei_Android\Assets\Plugins\Android" "-PMAVEN_REPOS=" "-PPACKAGES_TO_COPY="'
4. stdout:
5.  
6. ERROR: JAVA_HOME is not set and no 'java' command could be found in your PATH.
7.  
8. Please set the JAVA_HOME variable in your environment to match the
9. location of your Java installation.
10.  

In the documentation found here, it says that Unity is supposed to set the JAVA_HOME environment variable itself, which it did not. I know how to set it, but I don't know what to set it to because I don't know the location of the embedded JDK.

Additionally, Unity is deleting all of the plugins for Firebase and others found in "Assets/Plugins/Android" every time I launch the editor. I have not figured out how to get these to stop deleting, which is why I've been trying to use the Play Services Resolver because I've read that this tool is supposed to be what handles those things.

Any assistance you could provide would be of great help.

Thanks

 

I think still should use JDK8