Add visibility of proguard rules to README or wiki please
See original GitHub issueAre there examples of proguard rules that will work with minifyEnabled set to true? I’m currently getting:
java.lang.NoSuchMethodError: No virtual method doOnSubscribe(Lrx/functions/Action0;)Lrx/Observable
Issue Analytics
- State:
- Created 8 years ago
- Comments:28 (14 by maintainers)
Top Results From Across the Web
Diff - refs/tags/android-cts-4.2_r2^! - platform/external/proguard
@@ -1,6 +1,6 @@ <!-- This Ant build file illustrates how to process applications, by including a ProGuard-style configuration file. - Usage: ant...
Read more >A small, asynchronous IoC library for Android that might be ...
1. All classes that need to be injected must be annotated with @Component. · 2. Instead of adding @Component annotation to the interface,...
Read more >flutter_local_notifications 9.1.0 | Flutter Package - Pub.dev
A cross platform plugin for displaying and scheduling local notifications for Flutter applications with the ability to customise for each platform.
Read more >c1 · d09c2e044b - Gitea: Git with a cup of tea
Please provide additional information about the bug, if any. --> ... android/README.md View File ... +# Add project specific ProGuard rules here.
Read more >NextFaze / dev-fun Download - JitPack
Add it in your root build.gradle at the end of repositories: allprojects { repositories { ... maven { url 'https://jitpack.io' } } }....
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 Free
Top 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
@jaredsburrows You’re right, thanks for noticing. Seems like a dumb copy-paste error… Anyway, the proper settings should be:
On my code base (and yours too apparently),
BaseLinkedQueueProducerNodeRef
andBaseLinkedQueueConsumerNodeRef
classes altogether were stripped away by Proguard anyway so that no problem arose. For anyone whose code ended upBaseLinkedQueue
though, it would have probably thrown at runtime.@artem-zinnatullin Oh yes, forgot to add that - only switching Unsafe off on these problematic device - OS combinations.
@eranpolo Thanks the extra info. I’m still trying to get my hands on an affected device to get to the bottom of this.
Edit: for reference, our current naive workaround for the Samsung-issue: