You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see in consumer-proguard-rules.pro these lines.:
-keep public class * {
public protected *;
}
if we include this library in a multi module project, Proguard keep ALL classes, even those are not in this library. (Indeed Android Studio Plugin append all Proguard files)
What is the right way to keep the public classes of this lib? should i instead use
-keep public class de.mateware.snacky.* {
public protected *;
}
This seems much better, because it'll only affect the library code and not the entire project in which it is used.
With the current configuration I can't correctly obfuscate a project in which I'm using Snacky. This fix would be very much appreciated.
Activity
matecode commentedon Mar 1, 2019
What is the right way to keep the public classes of this lib? should i instead use
SebastianIRodriguez commentedon Feb 24, 2020
This seems much better, because it'll only affect the library code and not the entire project in which it is used.
With the current configuration I can't correctly obfuscate a project in which I'm using Snacky. This fix would be very much appreciated.
amarilindra commentedon Apr 9, 2020
Is the Proguard issue fixed in current version?
matecode commentedon Apr 9, 2020
changed the consumer proguard file, hope everything is fine now ... looking for feedback