Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Always use Proguard (in debug too!) #182

Open
dral3x opened this issue Mar 8, 2018 · 2 comments
Open

Always use Proguard (in debug too!) #182

dral3x opened this issue Mar 8, 2018 · 2 comments

Comments

@dral3x
Copy link

dral3x commented Mar 8, 2018

From my experience, is not good having too different configurations between debug and release, and this is especially true when Proguard is enabled only in one.

We found safer have minifyEnabled true also for the debug build, and turn off just the obfuscation (with a specific proguard-rules-debug.pro file).

You don't want to have your app running fine on your device while crashing on the user phone because you miss something in ProGuard configuration.

@rpattabi
Copy link

Makes sense. Only contention is the increased build time depending on the size of the project and dependencies.

@dral3x
Copy link
Author

dral3x commented Mar 12, 2018

@rpattabi that's true, I agree.
But since we're not in the javascript world, I prefer the "better safe than sorry" route

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants