I am using android studio to build debug and release application.
When i build debug/release application
./gradlew assembleDebug
./gradlew assembleRelease
both build are created perfectly and run as well. Shows appropriate dialog box for debug or release
now i have added proguard details in build.gradle:
signingConfigs {
myConfig {
storeFile file("keystore.jks")
storePassword "abc123!"
keyAlias "androidreleasekey"
keyPassword "pqrs123!"
}
}
buildTypes {
release {
runProguard true
proguardFile getDefaultProguardFile('proguard-android-optimize.txt')
signingConfig signingConfigs.myConfig
}
}
productFlavors {
defaultFlavor {
proguardFile 'proguard-rules.txt'
}
}
Now it shows error in event log as
Warning: there were 7 unresolved references to classes or interfaces.
You may need to add missing library jars or update their versions.
If your code works fine without the missing classes, you can suppress
the warnings with '-dontwarn' options.
(http://proguard.sourceforge.net/manual/troubleshooting.html#unresolvedclass)
Warning: there were 2 unresolved references to program class members.
Your input classes appear to be inconsistent.
You may need to recompile the code.
(http://proguard.sourceforge.net/manual/troubleshooting.html#unresolvedprogramclassmember)
:Flash Sales:proguardDefaultFlavorRelease FAILED
If i turn the runProguard option to false then its running.
I have these questions:
1) is it ok to release apk with runProguard = false?
2) How to use dontwarn while creating release build?
When I add new lib to project Generally this How I need to define for Progaurd.
Let's say I am using Twitter4J lib then I add dontwarn this way.
-keep class twitter4j.** { *; }
-dontwarn twitter4j.**
Put the -dontwarn lines in the proguard-rules.pro or proguard-rules.txt file.
Had to google this elsewhere since none of the answers included this info. Check the other answers for the specific lines you need for your case.
Related
I have added minifyEnabled=true to my 'release' build. The app runs correctly. And the androidTest apk runs correctly (all tests pass).
If I add any of the following to proguard-rules.pro:
-keepattributes LineNumberTable
-keepattributes LocalVariableTable
-keepattributes LocalVariableTypeTable
the app apk will build without error, but while building the androidTest apk I get ~4000 R8 "already has a mapping" errors for task:
:app:transformClassesAndResourcesWithR8ForReleaseAndroidTest
The (truncated) error log is
It appears that the methods that are getting the error are in 3rd party libraries (included as dependencies).
Thanks in advance for any help.
I solved the problem by adding an additional buildType for testing the 'release' configuration ('releaseTest'). It inherits from 'release', and sets debuggable=true.
buildTypes {
debug {
...
}
release {
...
minifyEnabled true // enable code shrinking & obfuscation
shrinkResources true // enable resource shrinking
...
}
releaseTest {
// inherit from 'release' buildType
initWith release
// for dependencies that don't know what 'releaseTest' is
matchingFallbacks = ['release']
debuggable true
}
I faced the same issue and adding
-dontoptimize
into my proguard-rules.pro just works for me.
I'm having some problems in building an Android app with ProGuard enabled.
This is the complete error:
Unknown option '-if' in line 16 of file 'C:\Users\Re\.gradle\caches\transforms-2\files-2.1\86eec96acf5ede717d441880a214115a\proguard.txt'
This is my build.gradle:
buildTypes {
debug {
manifestPlaceholders = [enableCrashReporting: "true"]
}
release {
minifyEnabled true
shrinkResources true
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
manifestPlaceholders = [enableCrashReporting: "true"]
}
}
And this is my proguard-rules.pro:
-ignorewarnings
-keep class * {
public private *;
}
I thought it could be a cache problem, so I've tried to Invalidate cache and restart Android Studio and I've tried also to clean the build cache with gradlew cleanBuildCachebut the problem persists.
If i disable ProGuard the build is successfull. What could it be?
Ok, I've solved removing some unused libraries.
I don't know which one was causing the problem but it has solved.
This question is related to a problem with my firebase, having the "debuggable true" option, which impact has in my program apart of enable testing?
When I configure another build or just the same but with "debuggable=false" the firebase can't be serialized. Why is this happening? Thanks
I though the proguard could be the solution but I'm using this build and changing debuggable to false is the problem.
Update
With proguard enabled or not, the result is the same with these permissions (I dont want any change in my code):
-dontwarn com.firebase.**
-dontoptimize
-keep class acr.acr_app.** { *; }
-keep class com.firebase.** { *; }
Gradle.Build
release {
minifyEnabled true
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
debuggable true
signingConfig signingConfigs.release
}
Udpate 2
I updated the libraries with no effect, somebody can help me a bit? How run app compile the app?
I am using Samsung's Motion library to create a pedometer for Samsung phones. When I create an APK without minification in the gradle configuration file the system works. However when I try to apply minification before releasing to the store,
buildTypes {
release {
minifyEnabled true
signingConfig signingConfigs.config
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
debuggable false
jniDebuggable false
}
I got errors claiming the some libraries (e.g. android.hardware.motion) do not exist.
I have checked and:
android.hardware.motion is not a standard library (probably existing only in Samsung phones?) in android.hardware
these classes are accesses dynamically (maybe because non standard?), e.g. Class.forName("android.hardware.scontext.SContextManager");
If I remove the line
minifyEnabled true
I got no error, so it must be the code obfuscation.
I have tried to add to my proguard rules file statements such as
-keep class android.hardware.** { *; }
-keep class com.samsung.android.sdk.** { *; }
but this does not seem to work.
Any idea? Thanks!
The missing classes are indeed only available on the actual device.
In order to let ProGuard process your application, you will have to include the following configuration:
-dontwarn com.samsung.android.sdk.motion.**
-dontnote com.samsung.android.sdk.motion.**
This will ignore the warnings and notes originating from the samsung sdk.
I'm trying to configure proguard to use it with my espresso UI test flavor. The thing is Proguard tends to ignore my debug proguard config.
This is how the config looks:
buildTypes {
debug {
minifyEnabled true
proguardFiles 'proguard-debug.pro'
testProguardFile 'proguard-debug.pro'
signingConfig signingConfigs.release
}
}
I added testProguardFile but it doesn't seem to work on androidTest. I'm running mockDebug flavor variant. When I just run the app it works fine, but when I try to run test which is located in adnroidTest it won't run due to proguard warnings, like the proguard file wasn't processed at all and the file is pretty straight forward:
proguard-debug.pro
-dontobfuscate
-dontoptimize
-dontwarn
Before someone starts to advise me turning off proguard for debug builds: I need to have it enabled because of multidex.
If you want your test build as close as possible from the real deal, try this one:
# build.gradle
debug {
minifyEnabled true
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
testProguardFile 'proguard-test.pro'
}
and
# proguard-test.pro:
-include proguard-rules.pro
-keepattributes SourceFile,LineNumberTable
On other hand, if you need it only because multidex, if your are using minSdkVersion < 21, ProGuard is tied to multidex flag and run automatically.
You also need to add the default proguard rules:
proguardFiles getDefaultProguardFile('proguard-android.txt')
This line can be removed, as it is a duplicate:
testProguardFile 'proguard-debug.pro'