I had ProGuard running for release builds when Cordova built with Ant, but now that Gradle is used my project's release builds aren't being obfuscated (my "cordova build --release android" output shows a step for :CordovaLib:mergeReleaseProguardFiles, but no other proguard/minification/obfuscation entries).
With Ant, my project.properties file referred to my proguard-project.txt file using the proguard.config parameter.
How do I configure this to work now that Cordova uses Gradle?
Have a look at the updated Proguard Documentation, you now have to change the build.gradle file.
Change the buildType release section to something like this
android {
...
buildTypes {
release {
minifyEnabled true
proguardFiles getDefaultProguardFile('proguard-android.txt'),
'proguard-rules.pro'
}
}
}
Related
I recently upgraded my hybrid MobileFirst app's mfp plugins to 8.0.20180408, and my cordova-android plugin to 7.0.0. When I did a debug build of the app, the build succeeded, but the moment I did a release build (signed apk) the process generated a lot of proguard warnings. When I downgraded the cordova-android version to 6.4.0 the release build succeeded.
The mobilefirst cordova plugin is supposed to support cordova-android v7 Since the MobileFirst iFix 8.0.0.0-MFPF-IF201804051553, as per the iFix release notes, but it seems that there is a problem with the it in this ifix.
I did some investigation into the proguard configuration file as there seem to be a problem with the gradle build process finding the right proguard configuration file.
The mfp cordova plugin contains a proguard configuration file called proguard-project-mfp.txt, which is added to the android platform of the hybrid project. The plugin also contains a gradle file
dev-build-extras.gradle
which specifies the location of the proguard configuration file. The proguard file specified in the configuration has no path attached to it:
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-project-mfp.txt'
It seems that in cordova-android 7.x, when the android platform is generated, it copies the proguard-project-mfp.txt file to the directory platforms/android/app/src/main/ whereas the dev-build-extras.gradle file is located in the directory platforms/android/cordova-plugin-mfp/
This means that gradle cannot find the proguard configuration file. Updating the proguard configuration file location in the gradle file relative to the gradle file seems to solve the problem and allows for the signed apk to be built.
In summary, update the file
platforms/android/cordova-plugin-mfp/dev-build-extras.gradle
with the following
// proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-project-mfp.txt'
proguardFiles getDefaultProguardFile('proguard-android.txt'), '../app/src/main/proguard-project-mfp.txt'
Your dev-build-extras.gradle file should now look like this:
android {
buildTypes {
release {
minifyEnabled true
// proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-project-mfp.txt'
proguardFiles getDefaultProguardFile('proguard-android.txt'), '../app/src/main/proguard-project-mfp.txt'
}
}
.
.
.
}
I want to build an .aar library and proguard classes, but my library proguard file doesn't work, and I can see clear classes.
Here is my proguard file:
android {
buildTypes {
release {
minifyEnabled true
useProguard true
proguardFiles getDefaultProguardFile('proguard-android.txt'),'proguard-rules-my-lib.pro'
}
}
}
and app/build.gradle:
android {
buildTypes {
release {
minifyEnabled true
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}
}
While you can probably shrink and obfuscate the library itself, the usual practice is to leave minifyEnabled as false and provide the proguard configuration to the application, using consumerProguardFiles instead of proguardFiles.
This means that the minification is applied only once, on the whole application, using the merged configuration from the app's proguardFiles and the libraries consumerProguardFiles. This is usually more efficient because parts of the libraries not actually used by the application can be removed.
Create a Android Studio Project and convert it to library Follow this link. Build and Execute the command Generate APK, .aar file will be created in release/debug folder.
Write the proguard rules as similar to APK, it will apply to .aar file also.
I hope this helps
Is it really possible to use ProGuard in Hybrid Application I am using Cordova version to build an android app where I have to obfuscate the plugin's java code.
Till now I have done this
Added
release {
minifyEnabled true
proguardFiles getDefaultProguardFile('proguard-android.txt'),
'proguard-rules.pro'
}
Inside build.gradle of project's root folder.
And uncomment the proguard line from project.properties
proguard.config=${sdk.dir}/tools/proguard/proguard-android.txt:proguard-project.txt
But nothing is obfuscating from the code when I decompile the APK.
I'm trying to use proguard but it keeps telling me to look for a project.properties folder and post this code
proguard.config=${sdk.dir}/tools/proguard/proguard-android.txt
the thing is I can't locate it. Where can I find it?
If you are using Android Studio then you will not have a project.properties file as it uses the gradle build system.
You can add ProGuard into your gradle build as follows:
buildTypes {
release {
minifyEnabled true
proguardFile getDefaultProguardFile('proguard-android.txt')
}
}
These lines should be automatically generated when you create a new Android Studio project, although minifyEnabled is set to false.
I am new to Android and Android Studio.
During my learning I came across the Google Play Services for Ads and all.
I tried to enable proguard in my project but reading the below link proguard.
The problem is that I am not able to find proguard-project.txt or proguard.cfg in my project structure...
Instead there is a proguard-rules.txt in my project structure...
How can I find these missing files and configure proguard in my project...
Please help...
Use the proguard-rules.txt file instead. Proguard doesn't attach any special significance to the name of its rule input files; it uses whatever's set up in your build files, which for new projects created in recent versions of Android Studio, is:
buildTypes {
release {
runProguard false
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.txt'
}
}
The proguard-android.txt file lives inside your SDK, and contains reasonable Android-wide defaults that all projects should use.
I had the same problem when I started using Android Studio
You can't see the ProGuard files because you are previewing you project in a non Project file mode. Which most probably will be Android view mode.
You have to change the mode by clicking on the drop down list of the Android selection and select Project Files to see all the files in the project as the following:
Then you will be able to see the hidden files in the Android project structure view mode.
And here is a good example for the ProGuard
You can find proguard-project.txt in
C:\Users\"USER"\AppData\Local\Android\android-studio\sdk\tools\proguard
"USER" is the name in you will see when you click on c-drive \users \yourname
the code posted previously must be corrected to the following according to your use:
buildTypes {
release {
minifyEnabled true //according to your use
// or
minifyEnabled false //according to your use
// runProguard false ** NOT USED ANYMORE, replaced by minifyEnabled
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}
I couldn't find this proguard-rules.txt anywhere on my Windows machine with Android Studio. I did however find a LayoutExample\app\proguard-rules.pro file. This is probably because I had imported my project from Eclipse, so Android Studio didn't create one automatically. So what I did was:
1 - Copy the proguard-rules.pro from the example project to the same folder as build.gradle for my project (you can either search for this file on your machine or create an empty project)
2 - Edit the code in build.gradle to use this file instead of proguard-rules.txt, e.g.
buildTypes {
release {
minifyEnabled true
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
signingConfig signingConfigs.release
}
}
Sync gradle, then Build > Build APK. Worked fine for me.
proguard-rules.txt can be found with terminal command on OS X (should be similar on windows as well)
$ locate proguard-rules.txt
On my machine the output is:
/Applications/Android Studio.app/Contents/plugins/android/lib/templates/gradle-projects/AndroidWearModule/root/proguard-rules.txt.ftl
/Applications/Android Studio.app/Contents/plugins/android/lib/templates/gradle-projects/NewAndroidModule/root/proguard-rules.txt.ftl
/Applications/Android Studio.app/Contents/plugins/android/lib/templates/gradle-projects/NewAndroidTVModule/root/proguard-rules.txt.ftl
/Applications/Android Studio.app/Contents/plugins/android/lib/templates/gradle-projects/NewGlassModule/root/proguard-rules.txt.ftl
You can place this file by removing the extra extension beyond txt. Here is what it looks like so you can create your own and place in your android project.
# Add project specific ProGuard rules here.
# By default, the flags in this file are appended to flags specified
# in ${sdkDir}/tools/proguard/proguard-android.txt
# You can edit the include path and order by changing the proguardFiles
# directive in build.gradle.
#
# For more details, see
# http://developer.android.com/guide/developing/tools/proguard.html
# Add any project specific keep options here:
# If your project uses WebView with JS, uncomment the following
# and specify the fully qualified class name to the JavaScript interface
# class:
#-keepclassmembers class fqcn.of.javascript.interface.for.webview {
# public *;
#}
I had the same problem after updating android studio , I couldn't import my project to new version.
change in the gradle build file.
buildTypes {
release {
minifyEnabled false *//change to this not runProguard false*
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}