android-proguard

the source code before compile&proguard : public class IntentSession extends BaseIntentSession { @Override public void onResume() { super.onResume(); mExecutor.exec(getIntent(), this::finish); } } the decompiled code after compile&proguard : (Decompiled with CFR 0_118) public class a extends superA { public void e() { super.e(); this.c.a(this.j(), b.a((a)this)); // the problematic code here } } now is the key code after compile&proguard, the b class's decompiled code : final class b implements c.a { private a a; b (a a1) { this.a = a1; } static /* synthetic */ b a(final a a) { return new b(a);

I'm trying to login with Facebook using ParseFacebookUtils library and it's working good but when i enabled the Proguard file i have this exception on Facebook login activity startup: Fatal Exception: java.lang.RuntimeException: Unable to start activity ComponentInfo{my.package.name/com.facebook.FacebookActivity}: java.lang.NullPointerException at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2413) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2471) at android.app.ActivityThread.access$900(ActivityThread.java:175) at android.app.ActivityThread$H

I'm using the Google Rest API v3 to connect my android app to Google Drive. When I run without Proguard (minifyEnabled=false), all is well. However, when I enable proguard the wrong REST API methods are called. When I call Drive.Files.get().execute on the drive root alias "root" I get the result for a Drive.Files.list().execute. When I disable "minifyEnabled" I see the correct result. Here is the section of the build.gradle that controls running Proguard: buildTypes { release { minifyEnabled true proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro' } debug {

Working with an Android project in Android Studio 3.2, having enabled Proguard and some specific rules, I'm not able to figure out the following: a specific package (and its subpackages) in a library module, used by client code, is preserved through the rule: -keep public class com.mylib.mypackage.** { public protected *; } Now, within this package there are also a number of package-private classes, which should not be picked by that rule. Some of those classes are effectively obfuscated, both in their own names and their member names, which is fine. Instead there are some classes,

I'm developing Android library and I want to hide/obfuscate the source code implementation of the library. The way the user project app will use the library is: startActivity( new Intent(context, LibraryActivityName.class) ); So I need to keep just the name of entry point Activity inside the library project, That's all. When I used the default ProGuard settings: buildTypes { release { minifyEnabled false proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro' } } as well as the suggested example for library - Nothing happened, and by clicking on the Activity name

In the new Google Play Services library (8.3.0) there is a new way to perform sign-in. This method involves adding the following dependencies: build.gradle (app level): classpath 'com.google.gms:google-services:1.4.0-beta3' And on app level: compile 'com.google.android.gms:play-services-auth:8.3.0' `apply plugin: 'com.google.gms.google-services'` When creating a release app version with minifyEnabled set to false , the app is being released and works fine. However, when creating a release version with minifyEnabled set to true the app crashes on startup with the following exception: java.lang