Develop Reference

How can I build an .aar library with shrunk classes in Android Studio?

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

Obfuscating code in android studio

Under minifyEnabled I changed from false to true.
buildTypes {
release {
minifyEnabled true
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}
}
Then I generated a signed APK and used javadecompilers.com to see if files had been altered and the classes,variables, etc were still the same.
I also attempted to use dex2jar, but the terminal stated that no files were found. I also attempted to export my android studio project as a jar file.
Any other suggestions ?

Did you build a release version of your application? As default for minifyEnabled is false, so if you build a debug version, that would explain it.
Other than that, could you post your proguard-rules.pro file? It might contain exceptions that are too broad.
I've used dex2jar many many times, and it's worked for me.
I'm on a mac, so i simply run "./d2j-dex2jar.sh app.apk" command, and then open the resulting jar file in a program called JDGui, there you can see all the files in the jar file.

AndroidStudio 2.2 build gradle error ( path to custom proguard file )

previous installed AndroidStuio version was :2.1.3 but after update to 2.2 and update gradle, building gradle has a problem Because of the proguard name.
Before, for release .Apk i use a custom proguard config with this way:
buildTypes {
release {
minifyEnabled true
proguardFiles getDefaultProguardFile('fileName.txt')
}
}
but after update AndroidStudio 2.1.3 to 2.2 this error occurs:
Error:(17, 0) User supplied default proguard base extension name is unsupported.
Valid values are: [proguard-android.txt, proguard-android-optimize.txt]
Open File
Notice That : After update settings and config files imported from previous version And SDK folder path not chnage
old way!
Unfortunately and finally, I had to use old version of AndroidStudio(2.1.3) and
this work but not is solution for AndroidStudio 2.2

way 1 :
After several tests I found that I should set complete path to proguard file like following config :
in build.gradle(module:app) :
buildTypes {
release {
minifyEnabled true
proguardFile ('FullPath/.../configFileName.txt')
}
}
, and no need to using getDefaultProguardFile before path.
Too , you can paste your config file to ...\appName\app and chanage proguardFile to :
proguardFile ('configFileName.txt')
Actually , default path is .../appName/app and if you put just configFileName , this will search file name in default project path.
in previous version I had't this problem and default gradle path was ...\SDK\tools\proguard
update
way 2 :
in below image and step 4 you can browse and select ProguardFile for debug or release
And in build.gradle(module:app) file , ProguardFile path will add automatically

try changing like the below
buildTypes {
release {
minifyEnabled true
proguardFiles getDefaultProguardFile('proguard-android.txt') fileName.txt // or file('{path_to_file}/fileName.txt')
}
}
guess it supports proguard-android.txt or proguard-android-optimize.txt for default proguard file as it stated in the message.
proguard-android.txt was located in ~/Library/Android/sdk/tools/proguard in my case.
I think android studio retrieve that file. or you may make proguard-android.txt in the project folder and add the path in getDefaultProguardFile parameter (I haven't tried it though).
After then you can add your additional proguard file by adding like the code above.

Proguard with Cordova Android 4?

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'
}
}
}

proguard-project.txt not found in android studio

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'
}
}