Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "proguard"
MOTHERFUCKING PROGUARD with all your fucking flags
-keep my ass
-dontwarn my balls
-dontshrink my asshole
FUCK YOU for all the hours I have to spend figuring out how to make you happy whenever I update guava or any other damn library GO FUCK YOURSELF
That new devlead that just joined and is bad mouthing everything we did and introducing his own state management library he hacked together without understanding our architecture (Clean Architecture) nor what layers are supposed to do and what the sense behind layers is. Also we learned from him that apparently Android deprecated ProGuard, LiveData is deprecated and Lifecycles in Android are broken.8
>building the same app once again because of a bug
>look in the unity editor settings for android
>google it, find it might be useful to minify, obfuscate code and other stuff
>try to minify the shit of the app
>original app was 25.1MB
>minified app is 24.6MB
>minified app using "Gradle (Experimental)" is 24.5MB2
FUCK YOU GOOGLE
I feel I have zero control as a developer.. You made the shittiest choice by bringing in intellij , you made an even worse choice by adding gradle.. You add thousands of configuration options to manifests, layouts but provide no common place to find documentation for them.. This is just nonsense.. I've wasted endless hours figuring out your dex limits, proguard rules.. It's just frustrating.. Could you be anymore counterintuitive with your unit testing framework! Honestly it's a steaming pile of shit..5
So after 11 years of Android development, the only solution for obfuscating app code aka proguard is so unreliable that you will be getting crashing apps in production , for a completely fine app in debug. Wtf
The other option is to use proguard in the debug too, so that you can handle the fuckups in the debug only, but that's going to make your build times jump to 10x slower from an already slow speed of 100 snail years/build.
Fuck you gradle. Ass fuck you proguard.5
A new Android app I made went from 100-ish users to 0 due to a mistake in ProGuard config causing crashes upon an incremental update... I'm losing motivation.. devRant, what should I do to gain it back? :(9
I hate tooling around Scala with libGDX so much - Gradle, Gradle Android plugin and ProGuard are just awful.
For example today I got during compilation: "Warning: Exception while processing task java.io.IOException: Please correct the above warnings first."
Grepping build log for (case insensitive) "warn" returns only the message above to correct warnings.
What the hell? I am required to correct not existing or invisible warnings or what? I hate you Gradle and ProGuard, I really do! >:(
Almost give up but finally found a solution to my problem, fucking proguard!!! fucking multidex, fucking limit of methods.... android -_-...