Library projects by themselves don’t run ProGuard, so they don’t use any configuration.
Application projects obfuscate the entire code base, including any referenced libraries, so they need proper configuration for the application code and for the library code.
More Related Contents:
- Proguard ignores config file of library
- How to make Proguard ignore external libraries?
- Best practice for storing and protecting private API keys in applications [closed]
- Adding a library/JAR to an Eclipse Android project
- DexIndexOverflowException Only When Running Tests
- Adding external library in Android studio
- How to remove all debug logging calls before building the release version of an Android app?
- Android studio add external project to build.gradle
- How to create jar for Android Library Project
- Enabling ProGuard in Eclipse for Android
- Android – java.lang.SecurityException: Permission Denial: starting Intent
- What ProGuard configuration do I need for Firebase on Android?
- Removing Log call using proguard
- Removing unused strings during ProGuard optimisation
- Publish an Android library to Maven with AAR and sources JAR
- BuildConfig.DEBUG always false when building library projects with gradle
- Debug native code in Android Library
- Android support multidex library implementation
- Convert existing project to library project in Android Studio
- Proguard warnings “can’t write resource [META-INF/MANIFEST.MF] (Duplicate zip entry)”
- Google Drive API doesn’t play well with ProGuard (NPE)
- How to change the proguard mapping file name in gradle for Android project
- Mopub ads not showing
- Android – How to check Proguard obfuscation has worked?
- How to create a release android library package (aar) in Android Studio (not debug)
- Android/java: Transition / Migration from ProGuard to R8?
- How to tell ProGuard to keep everything in a particular package?
- proguard.cfg file missing
- Gradle failed to build when proguard is activated
- can’t generate signed APK from Android studio “Execution failed for task ‘:packageRelease'”