Java – Configure the obfuscator to exclude library jars that extend android.content.Context

Configure the obfuscator to exclude library jars that extend android.content.Context… here is a solution to the problem.

Configure the obfuscator to exclude library jars that extend android.content.Context

I’m integrating a library into a device for a project that will be embedded in the device OS. To do this, we are integrating a library jar that overlays the Android framework context.

As a result, I get the following error when trying to enable Proguard for an application – “There are 220 instances of library classes, depending on program classes”.

All these files are widgets and views. How do I fix this?

This is what my proguard-project .txt

-injars      bin/classes
-outjars     bin/classes-processed.jar
-libraryjars /Users/me/android-sdk-mac_86/platforms/android-15/android.jar
-libraryjars libs/library-that-overrides-context.jar

-keep public class * extends android.app.Activity
-keep public class * extends android.app.Application
-keep public class * extends android.app.Service
-keep public class * extends android.content.BroadcastReceiver
-keep public class * extends android.content.ContentProvider
-keep public class * extends android.content.Context

This is what my proguard-android .txt

# 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);
}

-keep class * implements android.os.Parcelable {
  public static final android.os.Parcelable$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.**

Solution

Android Ant/Eclipse builds automatically specify all the necessary -injars/-outjars/-libraryjars options for you. If you have a custom build process, you should only specify these options. Otherwise, you get a lot of warnings about duplicate classes and other possible problems.

If you do need to specify the -injars/-outjars/-libraryjars option, classes specified with -injars can depend on classes specified with -libraryjars, but not vice versa. CFR。 ProGuard Manual > Troubleshooting >