Xamarin.Android Proguard - Unsupported class version number 52.0

30,159

Solution 1

You need to update the default Android SDK proguard.jar with the latest version of Proguard found here:

https://sourceforge.net/projects/proguard/files/

I would recommend that you install this on the side of the default version that Android ships in android-sdk\tools\proguard. Simply rename the existing folder to something else and add the new version of proguard.

This is listed in the Xamarin.Android 7.0 release notes:

https://developer.xamarin.com/releases/android/xamarin.android_7/xamarin.android_7.0/

In which the following bug was logged as well:

https://bugzilla.xamarin.com/show_bug.cgi?id=44187

Which is coordinated with a Pull Request in the Xamarin.Android repository:

https://github.com/xamarin/xamarin-android/pull/209

Solution 2

I had a problem where Proguard was removing the Google Play Services libraries from my app.

In addition to following @Jon Douglas' answer above, I had to add the following lines of text to the proguard-android.txt file found in this folder:

/(Path to your Android SDK Folder)/tools/proguard

-keep public class com.google.android.gms.* { public *; }
-dontwarn com.google.android.gms.**

Complete proguard-android.txt File

-keep public class com.google.android.gms.* { public *; }
-dontwarn com.google.android.gms.**

# This is a configuration file for ProGuard.
# http://proguard.sourceforge.net/index.html#manual/usage.html

-dontusemixedcaseclassnames
-dontskipnonpubliclibraryclasses
-verbose

# Optimization is turned off by default. Dex does not like code run
# through the ProGuard optimize and preverify steps (and performs some
# of these optimizations on its own).
-dontoptimize
-dontpreverify
# Note that if you want to enable optimization, you cannot just
# include optimization flags in your own project configuration file;
# instead you will need to point to the
# "proguard-android-optimize.txt" file instead of this one from your
# project.properties file.

-keepattributes *Annotation*
-keep public class com.google.vending.licensing.ILicensingService
-keep public class com.android.vending.licensing.ILicensingService

# For native methods, see http://proguard.sourceforge.net/manual/examples.html#native
-keepclasseswithmembernames class * {
    native <methods>;
}

# keep setters in Views so that animations can still work.
# see http://proguard.sourceforge.net/manual/examples.html#beans
-keepclassmembers public class * extends android.view.View {
   void set*(***);
   *** get*();
}

# We want to keep methods in Activity that could be used in the XML attribute onClick
-keepclassmembers class * extends android.app.Activity {
   public void *(android.view.View);
}

# For enumeration classes, see http://proguard.sourceforge.net/manual/examples.html#enumerations
-keepclassmembers enum * {
    public static **[] values();
    public static ** valueOf(java.lang.String);
}

-keepclassmembers class * implements android.os.Parcelable {
  public static final android.os.Parcelable$Creator CREATOR;
}

-keepclassmembers class **.R$* {
    public static <fields>;
}

# The support library contains references to newer platform versions.
# Don't warn about those in case this app is linking against an older
# platform version.  We know about them, and they are safe.
-dontwarn android.support.**

# Understand the @Keep support annotation.
-keep class android.support.annotation.Keep

-keep @android.support.annotation.Keep class * {*;}

-keepclasseswithmembers class * {
    @android.support.annotation.Keep <methods>;
}

-keepclasseswithmembers class * {
    @android.support.annotation.Keep <fields>;
}

-keepclasseswithmembers class * {
    @android.support.annotation.Keep <init>(...);
}

Solution 3

Simple Answer

According to documentation you need update proguard version (starting from version 5 it support Java 8 ) and make sure you are using jdk1.8

JDK 1.8 - up to API 24+

JDK 1.7 - up to API 23

JDK 1.6 - up to API 20

how to update from package console write this command

PM> Install-Package name.atsushieno.proguard.facebook 

https://www.nuget.org/packages/name.atsushieno.proguard.facebook

or download proguard manually and replace it with current version

YOUR_SDK --> tools --> proguard --> (delete all old files , unzip new version )

Detailed Answer if you enable target android Nogut and you enable Multi-Dex or ProGuard you need use proper ProGuard version (as ToolMakerSteve said they have dependency on ProGuard) so make sure you target java 8 from tools ->options ->xamarin ->java and update ProGuard version

Update Answer

make sure your support library version compatible with target version , if you target

Android 7 (api 24) mean your support library should be 24

Android 7.1 (api 25 ) mean your support library should be 25

to all support library and if you using google play services as well

Solution 4

I was also facing the same issue on my Windows 10 x64 and visual studio 2015. I have set the JDK path to JDK 1.8 under android settings in Visual studio tools ->options ->xamarin ->java development kit location. it was pointing to "C:\Program Files (x86)\Java\jdk1.7.0_55" and I made it to "C:\Program Files\Java\jdk1.8.0_31", and issue has been fixed.

Solution 5

Using Visual Studio

If you are using Visual Studio 2017 or 2019, please note that these applications pack their proguard. For 2019, proguard version: 5.3.2. For me, I needed version 6.0.3, so I made a backup of the proguard.jar file at:

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Xamarin\Android\proguard\lib

And copied the latest one from zip from the sourceforge site.

Share:
30,159

Related videos on Youtube

Eino Gourdin
Author by

Eino Gourdin

Updated on November 29, 2020

Comments

  • Eino Gourdin
    Eino Gourdin over 3 years

    I'm trying to use Proguard in my Xamarin.Android project, yet the compilation fails with the error Unsupported class version number [52.0] (maximum 51.0, Java 1.7)

    I saw from those two questions that it may be a mismatch between Java 7 and Java 8, more precisely some versions of proguard don't support Java 8. However in Xamarin Preferences -> SDK Location, Java SDK points to JDK 7 : /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home

    Is there any place where proguard can be configured more precisely ? Any other idea ?

    Here's the failure log :

    java.io.IOException: Can't read [/Library/Frameworks/Xamarin.Android.framework/Versions/7.0.0-18/lib/xbuild-frameworks/MonoAndroid/v7.0/mono.android.jar] (Can't process class [android/app/ActivityTracker.class] (Unsupported class version number [52.0] (maximum 51.0, Java 1.7))) at proguard.InputReader.readInput(InputReader.java:230) at proguard.InputReader.readInput(InputReader.java:200) at proguard.InputReader.readInput(InputReader.java:178) at proguard.InputReader.execute(InputReader.java:78) at proguard.ProGuard.readInput(ProGuard.java:196) at proguard.ProGuard.execute(ProGuard.java:78) at proguard.ProGuard.main(ProGuard.java:492) Caused by: java.io.IOException: Can't process class [android/app/ActivityTracker.class] (Unsupported class version number [52.0] (maximum 51.0, Java 1.7)) at proguard.io.ClassReader.read(ClassReader.java:112) at proguard.io.FilteredDataEntryReader.read(FilteredDataEntryReader.java:87) at proguard.io.JarReader.read(JarReader.java:65) at proguard.io.DirectoryPump.readFiles(DirectoryPump.java:65) at proguard.io.DirectoryPump.pumpDataEntries(DirectoryPump.java:53) at proguard.InputReader.readInput(InputReader.java:226) ... 6 more Caused by: java.lang.UnsupportedOperationException: Unsupported class version number [52.0] (maximum 51.0, Java 1.7) at proguard.classfile.util.ClassUtil.checkVersionNumbers(ClassUtil.java:140) at proguard.classfile.io.ProgramClassReader.visitProgramClass(ProgramClassReader.java:88) at proguard.classfile.ProgramClass.accept(ProgramClass.java:346) at proguard.io.ClassReader.read(ClassReader.java:91) ... 11 more

    9 Warning(s) 1 Error(s)

  • Femil Shajin
    Femil Shajin over 7 years
    Does changing the path fixed this issue??
  • Guillaume Perrot
    Guillaume Perrot over 7 years
    No it does not work for me, whether I use Java 7 or Java 8 in VS/Xamarin Studio I get the same error.
  • Guillaume Perrot
    Guillaume Perrot over 7 years
    This works for me, for the details I replace the Android tools/proguard/lib folder by the lib folder inside the latest Proguard release from sourceforge (5.3.2 at this time).
  • rooby
    rooby over 7 years
    If you replace the whole proguard directory, make sure to copy the config files from the old directory: proguard-android-optimize.txt, proguard-android.txt, proguard-project.txt.
  • ToolmakerSteve
    ToolmakerSteve over 7 years
    This does not fix the problem, if using ProGuard or Multi-Dex, because those depend on a tool inside android sdk/tools/proguard, as described in Jon Douglas answer. On the other hand, it should fix the problem for anyone not using either ProGuard or Multi-Dex, if they are getting this error trying to use Nougat [API 24], or some package/library that depends on an API 24 feature.
  • Darkmike
    Darkmike over 7 years
    The most fantastic thing is that it really helps even 2 years ago ) Thx man, you've saved my day.
  • Harshad Pansuriya
    Harshad Pansuriya about 7 years
    Thanks man you save my day. I wish I can give 100 up vote to you,
  • Emil
    Emil about 7 years
    this solution works even if you have the latest version. sometimes you may get the error, just redownload and replace with the existing. I dont know why but it works like that
  • Justin
    Justin over 6 years
    My android sdk folder doesn't contain a proguard folder, it doesn't even contain a tools folder.... And when I download the latest version of proguard, it doesn't contain a proguard-android.txt file so it errors on Xamarin build. What gives?
  • Jon Douglas
    Jon Douglas over 6 years
    @Justin Create a new Stack Overflow question with more details and I'll try to answer.
  • Chandler
    Chandler about 6 years
    Thank you very much @GuillaumePerrot Turns out replacing the whole proguard folder can not fix the problem but replacing the proguard/lib can.