android studio debugging stops working with proguard

But having a module with mixed Java & Kotlin code impacts on build speed. BuildConfig is generated as a Java file.Generating the BuildConfig file for each module has a build speed penalty.These are the main reasons to disable BuildConfig.java generation: It is typically located at src/main & src/release source sets.

when I say release code, I am talking about the code distributed on your release APK/AAB.It is typically located at src/main & src/debug source sets. when I say debug code, I am talking about the code available on the local builds used by developers when they pick the debug variant.It’s important to highlight that I am not talking about the app module BuildConfig, I am talking about all the other BuildConfig files generated by each android module.įirst of all, I would like to clarify some terms, so you better understand this article:

ProguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.This article will explain why I believe that generating the BuildConfig class for Android library modules is a bad idea. ProguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro' If you want to use your own proguard file then use the below rules.

proguardFiles getDefaultProguardFile('proguard-android.txt') to enable the default one.

Enable shrinkResources true to reduce the APK size by shrinking resources.

The obfuscated code makes your APK difficult to reverse engineer, which is especially valuable when your app uses security-sensitive features, such as licensing verification.īelow is a sample of how to enable default ProGuard in Android Studio.

ProGuard also optimizes the bytecode, removes unused code instructions, and obfuscates the remaining classes, fields, and methods with short names.

This will not provide just security to your code. I've asked many why they want to apply ProGuard to their projects, and I only encounter one answer, 'we use it only for security purposes'. Lafortune.Īs per the definition, proguard will help you to not only obfuscate, but also optimize, shrink, and remove unused instructions as well. It is able to optimize bytecode as well as detect and remove unused instructions. ProGuard is an open source command-line tool that shrinks, optimizes and obfuscates Java code. I have already provided my answer here, but now I want to explore what ProGuard is and how to enable it. Enabling ProGuard in Android Studio is a really easy task, but I am getting this question frequently on StackOverflow, which motivated me to write this simple article.

Android studio debugging stops working with proguard