proguard

proguard - AppCompat does not support the current theme features after proguard/minify

跟風遠走 提交于 2019-12-01 02:44:48
I've updated support libs to v23.0.0 from v22.2.1, after building app (with minifyEnabled true) i have "AppCompat does not support the current theme features" exception: 08-23 05:46:10.168 19437 19437 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{tm.alashow.dotjpg/tm.alashow.dotjpg.ui.activity.MainActivity}: java.lang.IllegalArgumentException: AppCompat does not support the current theme features 08-23 05:46:10.168 19437 19437 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2417) 08-23 05:46:10.168 19437 19437 E

Unknown classes ILicensingService notes when obfuscating Android project

旧时模样 提交于 2019-12-01 02:35:48
I'm trying to build an Android release with Ant and ProGuard. I uncommented the following line in project.properties, despite the comment in said file noting that you shouldn't modify it ;): proguard.config=${sdk.dir}/tools/proguard/proguard-android.txt:proguard-project.txt When obfuscating, I get the following notes: [proguard] Note: the configuration refers to the unknown class 'com.google.vending.licensing.ILicensingService' [proguard] Note: the configuration refers to the unknown class 'com.android.vending.licensing.ILicensingService' I do understand why this is happening. These lines can

ProGuard obfuscating classes even after `keep class` flag. Affecting Android WebView behavior

时光毁灭记忆、已成空白 提交于 2019-12-01 02:15:12
I'm using ProGuard to obfuscate my Android app. I'm also using WebView to show a webpage (an HTML walkthrough page) that contains a button that will close the WebView . There is a function in the Javascript that calls back a closeWalkthrough() method: function closeFunction() { MyClass.closeWalkthrough(); } The releated Java class looks like this: package com.myclass.android; import android.app.Activity; import android.content.Context; import android.webkit.JavascriptInterface; public class JavaScriptInterface { Context _context; JavaScriptInterface(Context context) { _context = context; }

Using “dontwarn” in proguard

不羁岁月 提交于 2019-12-01 02:07:49
问题 I use proguard successfully but whenever I add external library (those that belongs to advertising) proguard fails with "can't find reference ...etc". I tried many combination such as libraryjars, injars ...etc but no luck. Then I used the " -dontwarn " option on the external file and things worked magically. Is this bad to do? I mean is there a problem I am not seeing with handling external jars using this attribute? Thank you 回答1: For warnings about missing third-party classes, the options

Proguard ParseException with Default proguard.cfg on Android

大兔子大兔子 提交于 2019-11-30 23:42:35
I am about to release an application but, while i was building it using Export Tool of Android SDK in Eclipse, i get the error below. I didn't change the proguard.cfg. It is in the root folder of my project. I only add proguard.config=proguard.cfg to default.properties. I read the forum and update proguard (just copied the files to the tools folder of Android SDK), but still I doesn't work. I couldn't figure out what the problem is with the 'Projects\Eclipse' ?? If you help me, I will be so glad... [2011-08-08 02:32:46 - CoolProject] Proguard returned with error code 1. See console [2011-08-08

Setting ProGuard to obfuscate local variables and arguments

戏子无情 提交于 2019-11-30 23:27:16
I can't seem to find the setting that will obfuscate the local variables, inside methods of a class which is obfuscated. Here's an excerpt from one of the classes I've decompiled, with some obvious missing parts. Ideally, the arguments for the methods, and the local variables, would be obfuscated too. public class eA extends gu { private final gt a; private final gt b; public static boolean a(fy game) { boolean playerDead = game.k().j() <= 0; boolean enemyDead = game.g().a().size <= 0; boolean wavesRemain = game.r() > 0; return (playerDead) || ((!wavesRemain) && (enemyDead)); } public eA(gt

proguard - AppCompat does not support the current theme features after proguard/minify

浪尽此生 提交于 2019-11-30 22:39:40
问题 I've updated support libs to v23.0.0 from v22.2.1, after building app (with minifyEnabled true) i have "AppCompat does not support the current theme features" exception: 08-23 05:46:10.168 19437 19437 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{tm.alashow.dotjpg/tm.alashow.dotjpg.ui.activity.MainActivity}: java.lang.IllegalArgumentException: AppCompat does not support the current theme features 08-23 05:46:10.168 19437 19437 E AndroidRuntime: at

Proguard warnings despite kept classes

雨燕双飞 提交于 2019-11-30 22:39:16
I'm using Proguard to shrink my code. My strategy is to enable it and then follow the warnings to keep anything it complains about. If there are outside libraries, I try to follow the Proguard instructions the authors make available. Many instructions include a -dontwarn flag. If I disable the -dontwarn flag, I will get warnings. If we are keeping most classes via -keep flag, why do warnings still come up? Example: -keep class javax.** { *; } # for butterknife -keep class butterknife.** { *; } -dontwarn butterknife.internal.** -keep class **$$ViewBinder { *; } -keepclasseswithmembernames class

Android Proguard - how to keep onClick handlers only referenced from XML layouts

只愿长相守 提交于 2019-11-30 22:31:10
问题 In my Android app I ofter don't create a View's on-click handler in code, but rely on the ability to specify it in the XML layout file, like this: <Button .... android:onClick="onSearchClicked" ...../> And then have the method in the Activity like this: public void onSearchClicked( View v ) { ........} Meaning there is no obvious reference to this method in my own code. When running Proguard for a production release it seems to remove this method and the on-click fails. What can I add to my

ProGuard obfuscating classes even after `keep class` flag. Affecting Android WebView behavior

纵然是瞬间 提交于 2019-11-30 21:45:22
问题 I'm using ProGuard to obfuscate my Android app. I'm also using WebView to show a webpage (an HTML walkthrough page) that contains a button that will close the WebView . There is a function in the Javascript that calls back a closeWalkthrough() method: function closeFunction() { MyClass.closeWalkthrough(); } The releated Java class looks like this: package com.myclass.android; import android.app.Activity; import android.content.Context; import android.webkit.JavascriptInterface; public class