Basicly I\'m super newbie and started internship in IT company. I installed VS with Xamarin. The problem that I\'m facing is very frustrating. So even when i create empty pr
For me worked to change the SDK as well, but under Options->Xamarin->Android Settings, I don't have Cross Platform in Options for VS 2015Pro
In my case, i had to reinstall the JDK 8 (the last version) because other versions JDK 7 couldnt work even with new projects or clean up projects, and also i had to do a clean install of the android sdk.
I was having the same issue, and tearing my hair out. I had the JDK Version 8 installed, but these warnings wouldn't go away, and eventually they generated a build-breaking error.
When I went to Tools -> Options -> Xamarin, and looked at the Android Settings, the Java Development Kit Location was pointing to jdk.1.7.xxxx, in Program Files (x86)
.
I changed it to 1.8.0_101, in Program Files
. Then I restarted Visual Studio, and the same error happened again. Somehow, Visual Studio was detecting Version 7 of the JDK and pointing it to that automatically.
So the solution turned out to be very simple. As well as installing Version 8 of the JDK, UNINSTALL Version 7 of the JDK. As soon as I did that, Xamarin turned out to be much better behaved. This step solved a whole bunch of seemingly unrelated problems.
That error is telling you that the Java Class version that is being loaded was compiled with Java 8 (52) but Java 7 (51) is trying to load that compiled class.
Java 7 uses major version 51
Java 8 uses major version 52
Check which Java version(s) are installed on your machine and review Xamarin's requirements and Java installation steps (linked below)
Installing the Java SDK (JDK)
For people having problems with setting the appropriate JDK version, you might want to try to override this setting in the vs2015 options dialog:
You have a bad proguard.jar file, you need to replace this .jar by a correct version. The steps below describing how to do that. Some colleagues had the same problem here.
Everything should be fixed!
You can find more info about the bug here: