Bundled Android Proguard rules in 2.15 not taking effect
See original GitHub issueI’ve had -dontwarn com.google.errorprone.annotations.*
in my project’s proguard rules for a while now waiting for dagger’s consumer rules to be bundled. I saw a related PR was merged for 2.15 so I’ve tried building without that line in my project’s rules and I still get the same handful of “can’t find referenced class” errors pointing to that package that I was getting prior to 2.15.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Troubleshooting ProGuard issues on Android - Medium
The Android ProGuard rules include some safe defaults for every Android app, such as making sure View getters and setters - which are...
Read more >Shrink, obfuscate, and optimize your app - Android Developers
When you create a new module using Android Studio, the IDE creates a proguard-rules.pro file in the root directory of that module. By...
Read more >Vonage Video API Android SDK
Developer and client requirements; Creating your own app using the OpenTok Android SDK; Permissions; ProGuard rules needed by the Vonage Android SDK. Overview....
Read more >Proguard ignores config file of library - Stack Overflow
here is the first problem: even if minifyEnabled is false in the library, it gets obfuscated. it has no effect at all and...
Read more >ProGuard Manual: Troubleshooting - Guardsquare
If ProGuard is not keeping the right classes or class members, make sure you are using fully qualified class names. If the package...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That only fixed things for Bazel users. Bazel is not (yet) actually adding it to the aar though (it uses it in its internal implementation)
This is now in bazel, and at least working in 2.17, possibly 2.16 too.