Java 9 (JDK 9) support by Unity Android

On the scratch system macos high sierra 10.13 I've installed JDK 9 on by homebrew and Unity 2017.2.0f2 didn't work with it.

After it downloaded JDK 8 from Oracle site and changed path in Unity settings but the issue didn't solve.
After adding export JAVA_HOME=`/usr/libexec/java_home -v 1.8` to ~/.bash_profile it didn't work too.

Only full removing JDK 9 by command brew cask uninstall jdk - solved the issue

 

yarr weird it worked after uninstalling Java 9

running unity 2017.2.0f3 windows 10

 

Im finding that I can build with JDK8 but I cant sign my app. The passes are correct as shown in the console but I get:-

Code (CSharp):

1.  
2. CommandInvokationFailure: Failed to sign APK package.
3. D:\Android\android-sdk\build-tools\25.0.2\apksigner.bat sign --ks "E:/Shared Documents/Work/Android-KeyStore.keystore" --ks-pass pass:"keyStorePass" --ks-key-alias "appAlias" --key-pass pass:"appPass" "E:\Shared Documents\Work\MyProject\Temp/StagingArea/Package.apk"
4.  
5. stderr[
6. java.lang.UnsupportedClassVersionError: com/android/apksigner/ApkSignerTool : Unsupported major.minor version 52.0
7.     at java.lang.ClassLoader.defineClass1(Native Method)
8.     at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
9.     at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
10.     at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
11.     at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
12.     at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
13.     at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
14.     at java.security.AccessController.doPrivileged(Native Method)
15.     at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
16.     at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
17.     at java.lang.ClassLoader.loadClass(ClassLoader.java:412)
18.     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
19.     at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
20.     at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
21. Exception in thread "main"
22. ]
23.  

I have tried everything I can find, Reinstalling Android Studio, updating the JAVA_HOME environment variable, Deleting build-tools\25.0.2 (to force it to us 23.0.2), copying java.exe from System32 to SystemWOW64, (and other suggestions here ) But nothing works. Any ideas?

EDIT This was in 2017.1f1 by the way- I can even build an unsigned version in 2017.1.2 (see following post)

 

Also I just tried 2017.1.2p1 and that wont even build an unsigned version. I get:

Code (CSharp):

1. CommandInvokationFailure: Failed to re-package resources.
2. D:\Android\android-sdk\build-tools\25.0.2\aapt.exe package --auto-add-overlay -v -f -m -J "gen" -M "AndroidManifest.xml" -S "res" -I "D:/Android/android-sdk\platforms\android-23\android.jar" -F bin/resources.ap_ --extra-packages com.example.androidnative:com.example.an_googleplay:com.stansassets.androidnative:com.stansassets.mnp:com.google.android.gms.appinvite:com.google.android.gms.base:com.google.android.gms:com.google.android.gms.gcm:com.google.android.gms.iid:com.google.android.gms.plus:com.google.android.gms.tasks:android.support.v4 -S "E:\Shared Documents\Work\HURRARICE2017-u2017-1-2-Android\Temp\StagingArea\android-libraries\androidnative\res" -S "E:\Shared Documents\Work\HURRARICE2017-u2017-1-2-Android\Temp\StagingArea\android-libraries\an_googleplay\res" -S "E:\Shared Documents\Work\HURRARICE2017-u2017-1-2-Android\Temp\StagingArea\android-libraries\AN_Res\res" -S "E:\Shared Documents\Work\HURRARICE2017-u2017-1-2-Android\Temp\StagingArea\android-libraries\mobile-native-popups\res" -S "E:\Shared Documents\Work\HURRARICE2017-u2017-1-2-Android\Temp\StagingArea\android-libraries\play-services-appinvite\res" -S "E:\Shared Documents\Work\HURRARICE2017-u2017-1-2-Android\Temp\StagingArea\android-libraries\play-services-base\res" -S "E:\Shared Documents\Work\HURRARICE2017-u2017-1-2-Android\Temp\StagingArea\android-libraries\play-services-basement\res" -S "E:\Shared Documents\Work\HURRARICE2017-u2017-1-2-Android\Temp\StagingArea\android-libraries\play-services-gcm\res" -S "E:\Shared Documents\Work\HURRARICE2017-u2017-1-2-Android\Temp\StagingArea\android-libraries\play-services-iid\res" -S "E:\Shared Documents\Work\HURRARICE2017-u2017-1-2-Android\Temp\StagingArea\android-libraries\play-services-plus\res" -S "E:\Shared Documents\Work\HURRARICE2017-u2017-1-2-Android\Temp\StagingArea\android-libraries\play-services-tasks\res" -S "E:\Shared Documents\Work\HURRARICE2017-u2017-1-2-Android\Temp\StagingArea\android-libraries\support-v4-24.1.1\res"
3.  
4. stderr[
5. AndroidManifest.xml:28: error: Error: String types not allowed (at 'configChanges' with value 'mcc|mnc|locale|touchscreen|keyboard|keyboardHidden|navigation|orientation|screenLayout|uiMode|screenSize|smallestScreenSize|fontScale|layoutDirection|density').
6.  
7. AndroidManifest.xml:35: error: Error: String types not allowed (at 'configChanges' with value 'mcc|mnc|locale|touchscreen|keyboard|keyboardHidden|navigation|orientation|screenLayout|uiMode|screenSize|smallestScreenSize|fontScale|layoutDirection|density').
8.  
9. ]

I think thats the relevant part anyways- the log is epic, but after that it goes on about trying overlay files, finding them and processing them, but I dont see any errors there...tho like I say its the biggest log I have ever seen!

 

In AndroidManifest.xml find nodes with attributes `configChanges` (probably lines 28 and 35). Then try to narrow down (one by one), which item is not parsed as valid enum-value and thus treated as string: `mcc|mnc|locale|touchscreen|keyboard|keyboardHidden|navigation|orientation|screenLayout|uiMode|screenSize|smallestScreenSize|fontScale|layoutDirection|density`

 

Thanks for your reply...Trouble is, I dont actually have an AndroidManifest.xml file with that list of flags in it... I think something maybe generating it on the fly... (I'm using UltimateMobile which merges manifests for you, but none have a string like that in)
And also I am building with the same JDK and Android SDK in both cases above, so why is it only Unity 2017.1.2p1 that is giving me that error? Is it Unity 2017.1.2p1 that is generating that code with a flag that only exists in JDK9 or some newer buildtools (than 25.0.2) or something?

 

Well made a slight step forwards. I discovered that updating android studio made it store its updated sdk files in E:\Users\thisUser\AppData\Local\Android\sdk rather than its previous location. In there I see a buildTools folder with all the new ones. So I updated the Unity preferences location to that.

BUT it still doesn't work... Now I get:

Code (CSharp):

1. E:\Shared Documents\Work\PathToProject\Temp\StagingArea\AndroidManifest-main.xml:8:16-49 Error:
2.     Attribute application@icon value=(@drawable/app_icon) from AndroidManifest-main.xml:8:16-49
3.     is also present at AndroidManifest.xml:13:9-45 value=(@drawable/ic_launcher).
4.     Suggestion: add 'tools:replace="android:icon"' to <application> element at AndroidManifest-main.xml:8:3-48:17 to override.
5.  

But again I dont have any manifests that have an icon value defined as "@drawable/ic_launcher"

Ive now tried everything on this thread too, to no avail:
https://issuetracker.unity3d.com/is...ng-the-merging-manifest-files?page=2#comments

 

Manifests can be hidden inside `.aar`s of used plugins (try extracting `.aar` as zip-file).

 

Ok using E:\Users\thisUser\AppData\Local\Android\sdk rather than its previous location I cant build an unsigned version in Unity 2017.1.0.f1 either now...

So MONEY MONEY MONEY

what will it take to get some one to sort this building bullshit out for me. I need iOS too which is also not working- but was with the same project a couple of days ago (and for months before)

 

Ok found the culprit UltimateMobile Android Native an_googleplay.aar
and androidnative.aar

What can I do about that though?

 

thanks @JuliusM I finally got this working- I'm just gonna post what worked for me in case it helps anyone else- I'm not sure exactly which of these steps are 100% necessary but this is what worked for me on Windows 7...
1) Make sure you are using Unity 2017.1.2p1 (maybe greater, but I didn't try because I know Unity 2017.2 re-introduces a bug in meshCombiner that stops UMA from working)
2) Update your AndroidStudio/SDK via the download link in the Edit -> Preferences -> ExternalTools/ Android/ SDK Download button.
2a) I found after updating Android Studio all the sdk stuff had moved from my previous location, and it was now in C:/Users/YourUserName/AppData/Local/Android/sdk (My 'Users' folder is actually on my 'E:' drive but you get the idea) So make sure your Edit -> Preferences -> ExternalTools/ Android/ SDK is actually pointing to where your new SDK stuff _actually is_
3) Navigate to the above location and check in the 'build-tools' folder to make sure you have 26.0.2 in there
3a) If you dont have that, open Android Studio and go to File -> Settings, then in that window in the side pane twirl open 'Appearance & Behaviour / System Settings / Android SDK'
3b) Select the SDKTools tab in the window pane, ensure 'Show Package Details' is checked towards the bottom, and check 26.0.2 and hit 'Apply'. This should make that download and install. after that it should be in 'C:/Users/YourUserName/AppData/Local/Android/sdk/build-tools' If its not, your SDK locations is probably not right, because it will have downloaded it to an 'Android/sdk/build-tools' folder somewhere, so you are going to have to figure out where that is...
4) Update your JDK (Java Development Kit) *Dont* use the latest version (if you are on this thread I guess you already know jdk 9 is not working lol) instead go here (http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html) and choose the 'Java SE Development Kit 8u152' version.
4a) after you have installed that, right click on 'My Computer' or whatever its called now, goto 'Properties > Advanced System Settings' and click on the 'Environment Variables' button. In there look for the 'System Variables' section and find the variable 'JAVA_HOME' edit the value of that so it points to where you just installed Java 8 in the step above (in my case it was c:\Program Files\Java\jdk.1..0_152
4b) make sure that in Unity Edit -> Preferences -> ExternalTools / Android / JDK your path is set to the new JDK 8 you just installed.
5) Fix your AndroidManifest files. This will vary an awful lot depending on your project, but I was using UltimateMobile/AndroidNative and that was causing 'merge manifests' to fail during builds.
This is what they told me to do (and it worked):-

Code (CSharp):

1.  
2. 1) Open main AndroidManifest.xml by path: Plugins -> Android:
3. 2) Add this field xmlns:tools="http://schemas.android.com/tools" to tag <Manifest
4. 3) Then add this param tools:replace="android:icon, android:label, android:theme, android:debuggable" to tag <Application
5.  
6. ensuring that the <application tag actually has all those things eg android:icon="@drawable/app_icon" etc
7. 4) Finally open all other AndroidManifest.xml by path (for example): Plugins -> Android -> AN_Res and remove android:icon="@drawable/app_icon" android:label="@string/app_name" from tag <application

After all that I could finally build and sign my Android apps

Really hope that helps anyone considering throwing themselves off a tall building like I was!!

(now on to iOS lol...)

 

When can we expect the official fix?

 

This worked for me, I had the JDK 9.0 installed, I now have both the JDK 8.0 and 9.0 installed, added another path to include JDK 8.0 in the environment variables (Windows 10), and redirected that path in the Preferences window in Unity 5. It now works perfectly, thank you!

 

Ah, so that is why it wasn't building...

 

Changing JDK from 9 to 8 works for me.


Failed to compile resources with the following parameters:
-bootclasspath

Thank you Yury-Habets.

 

java 9 does not work yet any way to fix and i can not get java 8

 

Unity Guys, the tutorial on setting up android for unity is broken and no longer works. This is the tutorial I'm referring to: https://unity3d.com/learn/tutorials...ilding-your-unity-game-android-device-testing

The set up of the android SDK says to run the SDK manager but if you do it fails and says its obsolete. Anyone have a decent working set of instructions on how to instal the Android SDK that doesn't involve AndroidStudio please.

Particularly this step fails:

• Double click the file called android to run it.
  

 

I would prefer to use AndroidStudio but there are no instructions on how to integrate it into the Unity build process

 

I must be really thick. I'm trying to tell you the instructions for building Android in Unity don't work. They must be out of date. I installed AndroidStudio but where did it put the Android SDK? I can't find it anywhere. Does anyone have an up to date step by step instructions for how to install the Android SDK that Unity needs to build to Android.

Bear in mind if I knew how to do these things I wouldn't be needing Unity to do it for me.

 

I've got this now. I have Unity 2017.3.1f1
I have just install JFK 1.8u152 as instructed. I have SDK API levels 15,21,22,25,26,27 intalled on my E drive using Android Studio.
I set the toolset to, well, I've tried everything.
I have everything pointed to the various locations under preferences->external tools.
I have set the enviromnent variable 'JAVE_HOME' which didn't even exist before.
I still get the 'Unable to get target list...' error, and I'm about to throw the fecking monitor out the bloody window with a large deep roar!!!! - He says calmly and collectedly. - Someone please fix Android builds, otherwise what is the point of using this thing called 'Unity?'
Thanks,
Dave.
edit: Finally! Using this 'tools' set makes the error go away:- https://fossies.org/windows/misc/android-tools_r25.2.3-windows.zip/ but I had to delete the previous 'tools' folder in the sdk, I don't know why.
*note I have JDK 1.8 and 1.9 installed as I need 9 for something completely unrelated to Unity.

This is not a fix, it's a bodge with a bit of sticky tape and a couple of staples. Needs some proper work by Unity.
Also, please test Unity releases on a blank Windows install first, that way any legacy bodge work won't pass under the radar.

 

I've been 5 hours on this. Implemented each of the suggestions above. Still not working. Unity, we know it's other people's tools that are the problem, but it sure makes you look bad. You have made an incredible development tool but if people have to go through this just to build on Android, then I want to know, what else can I use?

 

I'm currently reinstalling Unity, Android Studio, and Java SDK. The bundle is not available any longer from Android, you have to install studio, open up the app, and then let it download the tools (it's not explicitly in the install wizard). I tried downloading the tools separately to no avail, going this route actually downloaded (like it used to) all the tools necessary. I guess they really want people using Android Studio :-/

BTW I am still using Java 8.0 as it works for me, didn't want to try 9.0.

 

This is what happened to me as well. I had to open Android Studio, and from there it prompted me to download the SDK.

 

This appears to not be fixed yet: I'm getting the issue with 2017.4 and jdk10.

http://www.oracle.com/technetwork/java/javase/downloads/jdk10-downloads-4416644.html

And just tried with 8 and I still get the same error. ((
http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html

Help?

 

For a solution please check my entry here:
https://stackoverflow.com/questions...avoid-build-failures-on-osx/49630166#49630166

 

Thanks but I'm not sure I get it.

How do I fix it on Windows and what does it imply? That I cannot use java 9+, like at all ?

 

OK, I'm uninstalling everything java related from my Windows 10.

What do I do to compile an android build of my unity project now?

 

it would be nice to have an updated list on what you actually need to build for android

 

There's this in the doc:
https://docs.unity3d.com/Manual/android-GettingStarted.html

 

Thanks for the painless solution GermanViscuso!!

 

Oh FFS.... It's May 2018.... Why on earth is Android still not working with a fresh download of Unity??

This is beyond a joke... And no I don't want to download specific versions, delete existing setups, rename folders... I use the Android SDK for other frameworks too... I'm not going to fudge it all up because Unity cannot get their act together....

Android Studio just works.. Xamarin just works... Flutter just works.... Why on earth months and months after being discovered that Unity DOESN'T just work ???

 

It's probably very helpful to explicitly note in the Android development documentation that currently only Java 8 is working and in case of problems to remove any existing jdk 9 or 10 installation (or at least try to change the jave home path).

It took me yesterday a few hours to identify that side-by-side isn't working, regardless of your jdk setting in Unity. This is especially frustrating if you're new to Android development.

 

So Unity 2018.1.0f2 still doesn't work with Java 9, 10?

 

Ahhhhh.. solved.. JAVA_HOME not set.. Really wish the error 'build failure unable to list target platforms' would have told me this.. ah well..

 

After being fustrated by this for the past couple of hours, what worked for me was to add the JAVA_HOME variable in Windows and MOVE the Android SDK from AppData and dump it into Program Files in a new folder in Windows. Build and Run, Unity asks to point to the SDK and point to the new location.