Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "android gradle"
-
> build.gradle == lifeispain
TRUErant dev life developer android studio pain pain in the ass gradle android android developer life is pain google1 -
Android development is like:
- 30% of the time is coding & debugging
- 70% of the time is waiting for Gradle to build16 -
Android Development be like:
- Has great idea for app or feature
- Boots up PC
- Starts android studio and creates new project
- Build error
- Gradle build failed
- Android studio crashes
- Java Error
- Shutsdown PC
- Goes and hangs himself
Pretty accurate if you ask me 😀😀😀😎18 -
Android studio gradle takes so much time to build. I decided to draw something to kill time whenever it build.
Day 3: Starlord is nearly complete.10 -
Me at the office, Boss calling me by phone..
Boss: Hi, I need a new Build of XX Android app for another client.. set the base address at x.x.x.x and send me an APK file
Me: OK, I will do it.
Boss: can you do it in 5 minutes?
Me: Sure, it's simple..
Android Studio: You think it's simple !
* Indexing Files
* Sync Project
* Gradle Build
* Indexing....
* Some f* tasks
Oh kill me now !!4 -
"Aah, time to make a new Android app"
*starts Android Studio*
AS: "Yo yo yo, before you proceed, update all these 512 things in your SDK"
*creates a new Activity*
AS: "Nuh uh, this shit won't work without this, install it"
*runs app on emulator*
AS: "Hoooold your horses, you need to install this, and this, and update this and this.. oh and also that"
*emulator finally runs, app crashes*
AS: "Ohh, ha ha, oopsies, your Gradle config is also screwed up, change every dependency to the newest version and then update them all"
*config finally done, runs again*
AS: "Umm, I am too lazy to sync it myself, so you must press the nice big button on top to sync it"
"Fuck this"
*closes Android Studio*
AS: "WAAAIT WAIT, before you go, a new Android update just showed up, you must upd..."
*alt+f4*5 -
*Le me Opening Android Studio
*Gradle building..
*Gradle building..
*Shit, cancel building, I need a simple thing
*Cancelling building..
*Cancelling building..
*Cancelling building..
*Cancelling building..
Oh kill me now !12 -
Problems with Android development
1. Android Studio is shitte
2. Android API is shitte
3. Gradle is shitte
4. Emulator is shitte
5. My life is shitte20 -
I finally built a new PC with 8GB memory, i7 4790K and SSD for OS.
My old system was a core2duo with 2GB memory. Android studio used to take 20mins for gradle sync and another 20min for signing apks. "Live preview" and "emulator" was a thing of the future for me. Never used it.
But now things have changed. This thing boots up in less than 5 sec and studio gradle takes less than 30sec. I'm so happy right now! Its like a dream come true! *cries in happiness*14 -
I have a little Gradle,
It's slow as f*king sin,
And when I'm on a deadline,
It loves to sit and spin.
Oh, Gradle, Gradle, Gradle,
It takes all goddamn day,
I guess I'll make some Ramen,
'Coz Gradle loves to play.
/rant9 -
I have been a mobile developer working with Android for about 6 years now. In that time, I have endured countless annoyances in the Android development space. I will endure them no more.
My complaints are:
1. Ridiculous build times. In what universe is it acceptable for us to wait 30 seconds for a build to complete. Yes, I've done all the optimisations mentioned on this page and then some. Don't even mention hot reload as it doesn't work fast enough or just does not work at all. Also, buying better hardware should not be a requirement to build a simple Android app, Xcode builds in 2 seconds with a 8GB Macbook Air. A Macbook Air!
2. IDE. Android Studio is a memory hog even if you throw 32GB of RAM at it. The visual editors are janky as hell. If you use Eclipse, you may as well just chop off your fingers right now because you will have no use for them after you try and build an app from afresh. I mean, just look at some of the posts in this subreddit where the common response is to invalidate caches and restart. That should only be used as a last resort, but it's thrown about like as if it solves everything. Truth be told, it's Gradle's fault. Gradle is so annoying I've dedicated the next point to it.
3. Gradle. I am convinced that Gradle causes 50% of an Android developer's pain. From the build times to the integration into various IDEs to its insane package management system. Why do I need to manually exclude dependencies from other dependencies, the build tool should just handle it for me. C'mon it's 2019. Gradle is so bad that it requires approx 54GB of RAM to work out that I have removed a dependency from the list of dependencies. Also I cannot work out what properties I need to put in what block.
4. API. Android API is over-bloated and hellish. How do I schedule a recurring notification? Oh use an AlarmManager. Yes you heard right, an AlarmManager... Not a NotificationManager because that would be too easy. Also has anyone ever tried running a long running task? Or done an asynchronous task? Or dealt with closing/opening a keyboard? Or handling clicks from a RecyclerView? Yes, I know Android Jetpack aims to solve these issues but over the years I have become so jaded by things that have meant to solve other broken things, that there isn't much hope for Jetpack in my mind 😤
5. API 2. A non-insignificant number of Android users are still on Jelly Bean or KitKat! That means we, as developers, have to support some of your shitty API decisions (Fragments, Activities, ListView) from all the way back then!
6. Not reactive enough. Android has support for Databinding recently but this kind of stuff should have been introduced from the very start. Look at React or Flutter as to how easy it is to make shit happen without any effort.
7. Layouts. What the actual hell is going on here. MDPI, XHDPI, XXHDPI, mipmap, drawable. Fuck it, just chuck it all in the drawable folder. Seriously, Android should handle this for me. If I am designing for a larger screen then it should be responsive. I don't want to deal with 50 different layouts spread over 6 different folders.
8. Permission system. Why was this not included from the very start? Rogue apps have abused this and abused your user's privacy and security. Yet you ban us and not them from the Play Store. What's going on? We need answers.
9. In Android, building an app took me 3 months and I had a lot of work left to do but I got so sick of Android dev I dropped it in favour of Flutter. I built the same app in Flutter and it took me around a month and I completed it all.
10. XML.
If you're a new dev, for the love of all that is good in this world, do NOT get into Android development. Start with Flutter or even iOS. On Flutter and build times are insanely fast and the hot reload is under 500ms constantly. It's a breath of fresh air and will save you a lot of headaches AND it builds for iOS flawlessly.
To the people who build Android, advocate it and work on it, sorry to swear, but fuck you! You have created a mess that we have to work with on a day-to-day basis only for us to get banned from the app store! You have sold us a lie that Android development is amazing with all the sweet treat names and conferences that look bubbly and fun. You have allowed to get it so bad that we can't target an API higher than 18 because some Android users are still using devices that support that!
End this misery. End our pain. End our suffering. Throw this abomination away like you do with some of your other projects and migrate your efforts over to Flutter. Please!
#NoToGoogleIO #AndroidSummitBoycott #FlutterDev #ReactNative16 -
Me: "If today's demo to the client goes well,i will get my first cheque"
My server:"If today i stop working,it will be great"
Android Studio: "If i force a gradle update,it will be just fine".
*crying*
Fuuuuuck.Why nothing goes my way when I want it to????Whhhhyyyyy??3 -
*To the tune of the Dreidel Song*
I have a little Gradle
It's building here all day
And when it's finally ready
I can begin to code and play
Oh Gradle Gradle Gradle
You're about as slow as glue
Gradle Gradle Gradle
You're making me feel blue
Oh Gradle Gradle Gradle
You're running on Android
Gradle Gradle Gradle
You're making me annoyed
Oh Gradle Gradle Gradle
You're going to make me cry
Gradle Gradle Gradle
I think I'm going to die
Why won't you work already
This isn't that damn hard
My temper isn't steady
Gradle you're a piece of lard11 -
That moment when you fixed all weird errors in Android Studio by frankensteining two projects together.4
-
*Adds new dependency*
Me: *Pray while syncing*
*Gradle project sync in progress*
*Gradle build finished in 9s 211ms*
Me: Thank you, Lord5 -
You've got to love Android development.. :D Just grabbed my laptop to start working on an idea I just had. Launched Android Studio to do some quick coding..
Update for the repo's..
Update for the IDE itself..
Update for gradle..
Started project. Need to update my build tools..
I.. I.. I just wanted to do some quick coding :D
*edit* Just tried to run the project.. "Acceleration driver is out of date, please update Haxm" .. Damnit..7 -
*Downloads Android Studio from the official Android website*
*Opens Android Studio*
Android Studio: "Error: Process command usr/local/android-studio/jre/bin/java finished with non-zero exit value 127
Me: I didn't even do anything yet. I guess I'll change the default Java directory to my native Java JDK
*One hour later*
Android Studio: 50 errors occurred during the Gradle Build.
Me: ( ._.)3 -
> Gradle build finished in 32 seconds
As if you did, fucking cunt. I've only watched half an anime episode and commented here and there in the meantime. Surely that'd be 30 seconds. Perhaps Gradle, you could've taken all that extra time to learn how to fucking count.
Android development, what hell am I getting myself into...5 -
Allright, I'm pissed.
Warning: more than 4k characters written by a non native english speaker ahead.
Legend:
Storytelling
> Short summary of the current situation
> "Something being said"
> (Something being thought)
* Actions *
-- Background --
In an attempt to reorganize my desktop I accidentally deleted a folder I called "development". In there I stored links to all my IDEs (Not sure how you call these in english), but also some workspaces like unity (Not much stuff there, processing (just some hobby stuff) AND Eclipse (FUCKING EVERYTHING RELATED TO SCHOOL WEB DEVELOPMENT). Now 3 days have passed and I realized this important folder was missing. Cleared that windows trash the instant I deleted the trash on my desktop.
> Shit, Regret
Install a file restore programm. Do every possible search. Nothing found.
> Big shit
Deadline was in like 3 days. Week was fucking rough so:
> "Screw this, the teacher nevet corrects the assignments and also fuck JSP"
Fast forward 2 months to last week. Teacher starts checking assignments.
> Fuck
* Sees pattern: Only students with missing or bad marks are checked. *
* Feels save *
Teacher approaching me while working on current projects.
* Doesn't feel save anymore *
> "Well, I'ld like to see your THAT programm"
> Well fuck
* Tells the truth *
> "Well that's unfortunate, but I must write a mark. Do you really have nothing to show?"
* Remember that I worked on the school pcs when I started *
> (Better than nothing. Gotta try it)
* Teacher checks programm, not pleased *
> (Fuck me, but at least it's over...)
> Nope
* Teacher calls me over *
> "With the mark I had to write today you can't reach that good mark even with a good examination, what are we gonna do about this?"
> "Well, there were other assignments that were never checked. Could we replace that mark with one of those?"
* Teacher agrees *
> (Srly bless this guy for that support)
My best choice was an Android app we had to develop during December in pairs. I did the front end (90% of the whole work) and my partner the backend (10 %). I also did 30 % of these 10 %, because I had to review the shit he wasn't able to debug himself.
> brainlogic.exe provided by windows vista
This distribution was partly my fault since I overestimated the work needed for the backend, but also the fault of that fucker. I mean, he didn't tell me the professor already provided 90 % of the backend...
Rest of the week was really busy (always 1 or 2 things to study for each day, workout and family stuff).
Yesterday (It's past 12 already) I arrived at ~9 pm in the dorm I could finally start reviewing my code.
Internet gets shut down at 10 pm.
Gotta hurry.
* Opens project *
* Sees half a year old code *
* Fights urge to puke *
> (Alright I gotta do this. For the mark!)
* waits for gradle to index files *
* Remembers the fact that I haven't opened Android Studio in the last 2 months *
For those who don't develop with android studio: This is an equivalent to ~10k windows updates waiting to be installed
> (Well, gotta work with this kinda old version)
"gradle sync failed"
> ( Ok, just restart it. You're fine )
* Android Studio doesn't react anymore and/or renders *
* Waits 5 min *
* Restarts laptop *
* Android Studio is reacting again*
"gradle is synching"
9:45 pm: gradle is done and I can finally compile my app
> FML
* Sees App launched on phone *
* Almost pukes again *
> (This was the assigment for the UX chapter, so design doesn't matter)
UX is decent. Proceeds with testing stuff. Save paths work, but some bugs can be caused by going of it
* fixes as much as possible *
* Takes quick look at backend *
Date date = new Date (GregorianCalender.getInstance().getTimeInMillis());
C'mon, I asked you to be the backend. You got 90% of the methods already written by the teacher and had 2 months to write the interfaces to my Front end AND you come up with shits like that.
Note: this example is a minor example of brainlogic.exe
I did what I could to make improve my situation. Hopefully he doesn't discover the bugs. And If it's a backend bug then I could't care less, since that was not my job!
Wish me luck for today!undefined web development jsp school assignment not my job fuck up android studio tldr; not getting paid enough for this shit gradle blame backend9 -
Le Me: well it is the time to go back on that Android project and resume the work.
*Open Android Studio, open the project.
*Wait 10 minutes for build/index
*error: gradle outdated, that is ok, update it.
*error: some library needs update
*error: R not found
*error: internal IDE error.
*Clean Project: PC hangs, Fan go so fast..
Shit ! I even not touched the code !8 -
PM: hows the android app going?
Android Dev: gradle downloading... blocked by network admin.
PM: anyway how is the iOS app going?
iOS Dev: cocoapods downloading... blocked by network admin.
PM: ... i guess the only thing running now is the web admin right?
Laravel/VueJS Dev: composer nodejs/npm/yarn downloading... blocked by network admin.
PM: team lets retest the api endponts
Team: Postman downloading... blocked by network admin.
Team: -_- Insomnia REST Client downloading... blocked by network admin.
PM: code study?
Team: even visual studio code/android studio/xcode is blocked. :(
.... sad dev life
anyone here with the same problem?14 -
Not a rant about anything in particular. Just a summary of some feelings stored in the hateful part of my heart.
Developing for Android: Add this third-party library to your Gradle build. Use (this) built-in Android class to make the thing work.
*Clicks link
Deprecated since API version SUCKMYDICK-7. Use (this) instead
*Clicks link
Deprecated since API version LICKMYBALLS-32. Use...
Developing for Windows: Please use (this) API call. It was literally already available before Bill Gates was born. Carbon dating has placed this item to older than the universe itself and it is likely the entry point for the big bang. It is also still the best way to accomplish (task).
Developing for Linux: "Hmm, I wonder how to use this"
> > > Some shitty mailing list in small blue monospace font tells you to reference a man page that is three versions behind but the only version available.
What? Those three sentences didn't explain it enough? Well, maybe you aren't cut out for this type of thing.
JavaScript: you know how it is.
SQL: You expect a decent-quality answer from stack overflow but you always get an outdated and hacky response and it's using syntax from Microsoft SQL. You need MySQL.
C#: A surprising number of Microsoft forum results ranking high on Google. You click on one in hopes that it will be of any sort of quality. You quickly close the tab and wonder why you ever even had hope.
Literally any REST API: Is it "query" or "q"? "UserID" or "user_id"? Oh, fuck, where's the docs again?
You thought you escaped JavaScript, but it was a trick!: Some bullshit library you downloaded to make your other library work redefined one of the global variables in the project you inherited. Now you get 347 "<x> is not a function" errors in your console. Good luck, asshole.
FontAwesome/ Material fonts/ Any icon font pack: You search "Close" for a close button icon. No results. You search "Simplified railroad crossing sign without the railroad". You get a close icon.
I think that's all of my pent up rage. Each of them were too small for an individual rant so I had to do this essay.2 -
Stuck on windows for a bit more now after my little Arch fuckup and holy shit I forgot how terrible running android studio on windows is...
*Opens project, waits for windows to unfreeze*
*Waits for gradle to load lets windows unfreeze*
*Opens AVD and watches RAM usage go to 100%*
*Sips now cold coffee that was made when opening Android Studio*
Ugh, I miss Arch...
PS. Yes I know this is an android studio thing and not a Wndows problem2 -
"i love the smell of possibility in the morning" i said.....
"Gradle build failed with errors"
--computer replied :)1 -
Ability to complaining about "Gradle is too slow in my laptop!" to my dad to get a better one.
Saying thanks to Google.3 -
Summer is coming, and i suppose all of you will buy a new barbecue to cook some meat, but i have another economic alternative.
How to make a homemade bbq:
1) Take an old laptop
2) Turn it on
3) Install Android studio (also works with intellij)
4) Add a lot of gradle (or maven) depencies
5) Code something cool (or not)
6) Build and compile it
7) Now you can put your meat on your laptop
8) Enjoy your meal13 -
I know people complain about Android Gradle takes so long to build (and I know the reason why, thanks to @DRHAX34) but for me that isn't what I have to wait for.
It's the shitty WiFi at work that causes issues/bugs I'll never experience normally lol
When my app builds I have to also connect to the internet and check for updates against the umbraco server, and it works if it fails to connect (naturally) but our internet somehow manages to stay connected enough to trick the app into doing continuous checks or some form of tiny and long downloads
I've been tempted and sometimes do use my own mobile data which would waste my tiny data (at the time)
Anyways fuck you shiternet lol -
Sometimes, I think Android Studio is using my resources to actually mine bitcoins whenever there's a grade build.2
-
My Android Studio couldn't build Gradle even after fuckin' 42 minutes. Finally I had to force stop it.8
-
Better gradle they said.
Builds faster they said...
There is a difference between faster and less slower.4 -
I always thought android people were just a little bit whiny, but now that I'm developing an app in my free time I feel you.1
-
My day:
Creates flutter project.
Gradle failed
Update Android studio and gradle
Gradle failed
Uninstall a Android studio (at least I thought I did)
I install Android studio
Gradle failed
Repeat least three steps 2x
Gradle works!
Flutter failed.
:(3 -
Feels like I found value of "NAN"
i.e, finding non-ranter dev @ devrant!
"Write no rant
Comment no rant
++(view) all rant "
@Ghored
I guess he should be given a badge or something!
Never able to achieve that stage of satisfaction,
Bsod in windows,
Grub rescue for Linux,
Gradle build problem for android,
404 errors,
What not ?
Yet I really feel like today , I met a ironical legend of dev community!
A full bow to you my friend4 -
Honestly fuck Android development and gradle. If I have a perfectly fine build from 6 months ago I expect it to still be working when I need to update two lines. FML4
-
Dear Gradle,
I just modified a single attribute value in an XML. Please!!
You just built the whole thing a few minutes ago.. Why do you wanna... Oh well...
Gradle build running....7 -
That moment when you try showing an issue to your senior developer and gradle takes forever to build.
Clicks build...
Goes to get coffee.
Takes a sip.
*1500 sips later*
Gradle build still running...2 -
If you start your Gradle build at 11:50 pm on New Years Eve, you'll be able to start resolving your compile time errors by the time the clock strikes midnight.
Kick off 2018 the right way.3 -
Making my android application in like 9 months.
Feeling good, except that Gradle is hanging in my 16GB RAM, is it required to have 512GB?6 -
I sat down at 7pm to work on my app. Pull from Github, have a million gradle errors even though literally nothing changed, and Android Studio wants to update itself and the whole sdk. Long story short, it's now 9:56pm and I'm praying gradle doesn't fail so I can finally get to work on something...4
-
The advantage of programming in Android studio is that you can read a chapter of your favorite book, watch a series or do a little exercise... Thank you gradle2
-
Holy shit android development is hard. I mean, either I'm spoiled with my packet managers in web development, or gradle just sucks.
I know these things have learning curves but jesus christ it's like hitting a brick wall.6 -
I really like Kotlin as a language, but Gradle makes me feel nauseated.
Pulling in deps without getting errors, then the library won't resolve because of some version mismatch (still, no error or warning on build, until I try to import the dependency in the code, and then just "unable to resolve <library>" without details). All of the documentation on the internet is either super specific for Android projects, or for an ancient Gradle version. Feels like I'm back in Haskell's "Cabal Hell".
*runs back into the loving embrace of Cargo*.
What was I thinking, trying to write an application in something that's not Rust.5 -
Android dev rant:
>Fixing some code
>Compile code
>Take a walk, waiting for gradle to finish compiling
>Almost 10 mins, notice typo on code, while still running gradle
>Fixing some code
>Compile code
>Take a... Wait a minute11 -
So today installed this plugin on all my compatible JetBrains IDEs:
https://plugins.jetbrains.com/plugi...
Especially as an Android dev I look at Gradle build progress bars about 99% of the time, so better make them look great while I'm at it.7 -
hey there I'm developing an android app,
started the work back in 2013 ,
waiting for gradle to finish the build
#androiddeveloper -
Last week's Android development time breakdown:
21.9% Managing state
17.7% Referring to lifecycle diagrams
15.1% Waiting for Gradle
8.5% Reading the official docs on how to use component x
8.4% Reordering auto-generated ConstraintLayout XML
7.5% Swearing
4.2% Googling “Stack overflow component x is deprecated”
3.9% Googling “Stack overflow implement component x on API 24 or lower”
3.7% Googling “Stack overflow implement component x on API 21 or lower”
3.2% Googling “Stack overflow implement component x on API 19 or lower”
2.9% Googling “Stack overflow callback y called twice”, realising its a feature and not a bug, swearing a lot
2.0% Checking if Flutter is mature yet
1.0% Implementing business logic4 -
FUCKING FINALLY TIME!!!
I did it! I made IntelliJ IDEA find my Android SDK installation!
Thanks SO!!!
Now I can experience the joy of Gradle build times!!!
Why did Google had to make so difficult to work with Android without its Studio?!?!?!12 -
Gradle build, gradle build,
Builds whatever a gradle builds
Builds projects, any size,
Catches errors just like flies
Look ooooooout!
The gradle build has failed5 -
Never start watching a series while gradle is building. You end up not finishing coding your app on time instead you watch a whole season before you get back to coding.3
-
I have a dream...
I have a dream that one day my children will be able to wake up and install a fucking react native library without gradle losing its absolute shit3 -
With Android Studio, 90% of time I am stuck waiting for gradle builds to finish, and 10% of time I am too pissed to code anything.4
-
Fuck android studio in the ass with cactus.
*starts learning Android*
*Builds simple application with 1 Button, 1 TextView and 1 EditText*
At this point, I haven't implied any logic or code in MainActivity.java.
*Hit Run*
*Gradle Build*
*Meanwhile, eat lunch*
*Still Gradle Build*
*After 2 Eternity, Build finished*
Fucking, slow peice of shit. I'm rebuiliding the App, because the AVD timedout while running.18 -
I was using chrome + Android studio simultaneously on my windows. I saw 3 episodes of 'friends' while my Gradle build finished.2
-
>Installed Windows 10 Insider Build
>Opened Android Studio
>*creating Gradle project info*
>BSOD
:(2 -
So lets start here, as i have been preparing myself for a while for that rant. I have been putting it off for a while, but today I had enough.
Fuck react-native and fuck facebook react-native team. Bunch of lazy incompetent twats.
The all amazing framework that suppose to be speed up your development process, since you don't have to compile your code after each change. SO FUCKING WHAT if the god damned framework is so fucking buggy and so fucking shit that you constantly have to fix build, dependancies etc issues. Every day since I work on this project that is using react-native I have to deal with some of the react fucked up behaviour. You got an issue ? don't worry google it just to find out that 100 other people had the same issue. Scroll through down the bottom of the page just to find out that facebook devs have closed the issue as resolved (without fucking fixing it) because there wasnt recent replies to the post. Are you fucking kidding me? It's ok thou, create a new issue just to get an automatic reply from the bot that locks the thread and keeps it locked till you update your React-native version to the newest one. You do that and guess fucking what? Their newest version fucks up remote debugging on iOS(fucking android been broke for over a year) so say good bye to debugging your js code. Documentation is fucking trash. You found a nice function like autoCaptialise on your text input? Great! Ah wait, its not fucking working, what is wrong? You google this just to fucking found out it, function never worked on android, so why the fuck you still have it exposed and still have it in your docs? You want to add package? So fucking ez, just type npm install <name of the package>. Ha! fuck you, you still have to go and add them fucking manually in gradle in android and in pod in xcode, because obviously react-native is a one big fucking bullshit. Oh and a scroll view is a fucking glorious highlight of that framework, try add some styling to it, you gonna have loads of fun. Fuck react-native. And fuck the fucking idiot who convinced my boss that framework is so fucking great and now I have to work on this shit. Sincerely Xamarin Developer.9 -
Oh my motherfucking God...
How the fuck can a dumb IDE be so fucking slow? I entered the office at 8:15. And I am still unable to checkout a motherfucking previous version of an android app in git and get Android studio to build it, because the fucking gradle is so damn slow it freezes the GUI. WHAT. THE. FUCK. Android studio get you shit together and maybe, just maybe don't be such a dick!!!
You need 5 min to open that project and another 10 to build it ONLY FOR ME TO REALIZE THAT I HAVE TO REPEAT THAT WHOLE PROCEDURE BECAUSE I NEED A DIFFERENT APP VERSION FROM THE GIT REPO FUCK YOU YOU SHITFACED STUPID COCKSUCKING CUNT, SHIT FUCK ARRRRGH!!!
Sincerely,
Me.
Edit: now it's 9:35 btw6 -
Why the fuck is android studio such an unoptimized POS?
It sucks up resources like a sponge.
And Gradle just pushes the cores to the max.
Simulator is a memory hogging Pos too.
I had to buy a new laptop just to run it faster.
I had
AMD A8 4500M
8gb ram, running on Ubuntu.
Now I have macbook-pro 15 in. And it still can ramp us the fans.
Ffs get your shit together jetbrains.15 -
So this happened with me today.
Me: Will you be Gradle of my Android Studio?
Girl (Designer): I can't build you.
Despite the negative, my affection increased twice fold on her now. -
I always thought the gradle icon in Android Studio was a mouse with its tail. Yesterday one of my colleagues told me that it was an elephant. Never realized it until now 😐4
-
1. Hits "Run" in Android Studio.
2. Goes to make coffee knowing Gradle will take a while to build.
3. Comes back after 30 minutes.
4."Select Device"
Fuuuuuuck!😠😠5 -
*Furiously cracks fingers and starts typing*
When I first tried out mobile app development some weeks ago I found it pretty fun. Now when I have a internship with a company to create a Android app I was kind of excited. Now after just a week I don't think I will come back to Android development again. Android studio eats my RAM and made my computer hang itself, and the thing I despise the most is gradle! AS f**ks with my gradle also so now they are all gone and i'm trying to rewrite them by myself...
*Furiously tries to calm down*10 -
hey... can I build a FUCKING android image that uses a camera library?
react-native-camera: deprecated, no longer maintained
react-native-vision-camera: it's like globalthermonuclear war with versioning and patches and support and splat splat bullshit in that repo, don't even dare look at the issues there, trust me, please
react-native-camera-kit: doesn't compile for targetSdk 33, no matter what the FUCK you do
jesus christ i want to scan a fucking QR code with my app and my gradle configs have turned into world war III where the fuck did we go wrong folks8 -
"No signature of method: build_4z0stktnpkjsyfd6ol74tcab1.android() is applicable for argument types: (build_4z0stktnpkjsyfd6ol74tcab1$_run_closure2) values: [build_4z0stktnpkjsyfd6ol74tcab1$_run_closure2@5edbe9fa]"
Thank You gradle. This is very useful.... FML2 -
I can literally remember back in January 2015 when android studio was a fat piece of slow SHIT and to boot up an emulator it took me 5-20 minutes. Gradle build took 1-2 minutes. I was dying.
Now 4 years later in 2019, it still might be fat but godfckindamn it is fast. Emulator boots up in 2-4 seconds. Gradle finishes in no more than 6 seconds. Hierarchy opens up in less than a second. Performance statistics and analytics no longer lag or have latency.
Google has finally done a great fckin job fck u thnx3 -
In a conference video call of our tech team, someone remarked how he used to believe his laptop is so powerful until the day he installed Android Studio. To which I remarked, it takes somewhere around 10seconds on my machine to build this up. No wonder it became a butt of jokes, someone would say my laptop has a nitro-booster, or I build Hello World Programs. I literally had to show them screenshots and gradle build logs.
-
Motherfucking Android Fucking Studio. Just told me there is an update for the fucking simulator, and after the update it refuses to even sync. Fuck!8
-
I left class early today
I understand me and this kid are both students and both of us are still learning. But when he asks me to help him solve an issue I fucking expect him to listen then try what I’m saying unless he knows for certain that my idea won’t work
I don’t expect him to start ignoring the person HE asked for help to try things on his own and end up DELETING THE FUCKING GRADLE FOLDER because the 1.5.1 version of Android studio my teacher makes us use told him gradle was corrupt
I also didn’t expect him to tell the professor I didn’t tell him not to And them end up with the professor fucking assigning me to help him fix everything even though the kid won’t listen to me anyway refusing to just copy he java and XML to a new project so I grabbed my stuff and left Fuck that bullshit
I understand we’re both students and in the grand scheme of things we’re both idiots. But when I’m asked for help I expect the person to at least listen and not do something absolutely stupid like delete something we don’t understand how to fix
Now I’m making common sense a requirement to ask me for help I don’t need any extra stress I’ll deal with the consequences of walking out tomorrow But I can’t say I regret it1 -
Fuck you Android Studio. You just prompted me to update, and now are saying The project is using an unsupported version of Gradle. Why the fuck did you not update Gradle (whatever the shit it is) yourself?
What was wrong with Eclipse? Why the fuck Google decided to move to this piece of crap?14 -
>building the same app once again because of a bug
>look in the unity editor settings for android
>find "proguard"
>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 -
Writing code an testing it: works fine.
Not touching it for 3 weeks: can't compile it due to an gradle error
I hate Cordova!10 -
What the f*** is this gradle in Android Studio??
M getting tired with this error. Whenever m starting studio it stuck on waiting for build to finish project.. I already done with checking offline work still it's not working.. What the f*** should I do with this error??9 -
*cloning and building this other team's Android project*
"install API 21, current is 23" K
"needs gradle wrapper 2.2, you have 2.10" umm, OK
"this project is using gradle 1.2.3, current is 2.1.1". (ノ-_-)ノ~┻━┻ -
Fuck Android Studio and Gradle!
Especially Gradle, you fucking slow RAM consuming shit!
It consumed like all of my RAM and my computer is lagging like shit
It can't even import my SVG!
Because of frustration I accidentally hard reset my local git repo and lost 3 hours of work!8 -
So I made an update to my React Native app. I changed UI of a couple of screen, added a few animations here and there, refactored how my graphQL resolvers work in the backend(no breaking changes), changed how data gets loaded into the database etc.
It worked in dev so I figured hey let's deploy it. Today is(was because it's now 3am but more on that later) a national holiday so no one goes to work so no one will use my app so I have an entire day to deploy.
I started at 15:00(because i woke up at 13:00 lol). I tested the update once again in dev and proceeded to deploy it to prod. I merged backend to master, built docker images, did migrations on the db, restarted docker-compose with new images. And now for the app. I run ./gradlew assembleRelease and it starts complaining that react-native-gesture-handler is not installed. Ugh, rm -rf node_modules && yarn install. It worked. But now gradlew crashes and logs don't tell me anything. Google tells me to change a bunch of gradle settings but none of them work. Fast forward 5h, it's around 20:00 and I isolated the issue to, again, react-native-gesture-handler. They updated from 2.2.4 to 2.3.0 which didn't fucking compile. 2 more hours passed (now 22:00) and I got v2.3.1 working which fixed the problem in 2.3.0 but made my app crash on startup. YOUR FUCKING LIBRARY GETS 250K WEEKLY DOWNLOADS AND YOU DONT EVEN BOTHER CHECKING IF IT COMPILES IN PROD ON ANDROID?! WHAT THE FUCK software-mansion?
After I solved that, my app didn't crash. Now it threw an error "Type errors: Network Request Failed" every time I fetch my legacy REST API(older parts use rest and newer use graphql. I'll refactor that in the next update). I'll spare you the debugging hell i went through but another 5h passed. Its 3am. My config had misspelled url to prod but good for dev... I hate myself and even more so react-native-gesture-handler.3 -
I don't know If I should blame Gradle and the Android emulator for my computer freezing (cuz out of memory), or I should blame myself for not having a powerfull enough comouter?12
-
Well, look at the brighter side Android developers, that long time gradle takes to build gives you the much needed break, doesn't it?undefined gradle sync my ass android studio time wasted android dev android gradle gradle kills on i34
-
Took over an Android Studio project with Gradle. Here are my results:
Time to make code changes: 1 hour
Time to setup, configure, and build app: 1000 years -
My relationship with Gradle is like a couple who are only together for the kids. Some days are hell and some days are okay, but rest assured there is no love there.1
-
I was working on an android project this morning.I started android studio.
I went and made a cup of coffee and had it,came back still gradle was building -
It could just be me, but I feel lime I have an extreme lack of money to pursue projects. I know java really well, but I want to develop android apps. That's fine until you consider the fact that the only computers I have available to me at my house are very old. A gradle build in android studio on my PC takes <10min. So I just really need a better computer which means I need money which means I need a job which is unlikely because not many people hire 15 year olds. In fact, my parents bought a laptop last year for me to use, but my older sister fried the video out component on the motherboard so it needs a new one which is ~$3001
-
Please update your Android Studio or your computer to the newer versions and stop ranting about Gradle build time.
Please!!!2 -
Not sure if it is because my computer is older, but my demo app is taking forever for gradle to build! Now I can procrastinate without feeling bad! 😁😁
-
To Android developers:
ALWAYS use annotations for service classes when using minifyEnabled option in build.gradle!! I learn it in the hard way 😐 -
/rant on
React Native is BS for Android. Outdated as hell Gradle builds (1.x for certain plugins I mean wtf) and it targets outdated SDK and build tools... Why no simply code for system your software is meant to work :P
/rant over
In seriousness, I get the concept of build once deploy on all platforms ala Electron but better but hell why is the tooling so outdated?1 -
Was recently in a motorcycle accident and haven't been cleared to go back to work yet so I'm trying to build my first Android app.
I don't know Java, XML, kotlin, Android studio, or what the fuck a Gradle is; but I figured I'd take my app idea and download Android studio then try winging everything from there.
Needless to say, I'm having a damn hard time lol. I have been watching firebase tutorials on YouTube to try and figure out how to add authentication to my app. I kinda got it working in the AVD. But my personal Google account has 2FA enabled so I can't seem to get the app to sign me out, or sign me back in. (I was able to authenticate once successfully.)
I have no idea if having 2FA enabled is even the problem. I tried turning on debugging and can't seem to figure out how to actually get the app to debug or get a debug console open.
I seriously feel like the world's biggest n00b right now. Going to go YouTube/Google how to get the debugging working. Then I'm off for a round of learning how to read a debug report!
Hahahaha... Kill me now -_-'2 -
When you click Run, go for a coffee, have a meetup, a quick nap, grow a beard and two kids only to come back and find ...
...Gradle building... -
Every. Single. Time. I've tried to learn and implement proper Unit/Instrumentation testing, the main Android devs decide to go for something else or introduce some feature or Gradle plugin that breaks every tutorial out there. I find it way easier to just test everything manually than learning the new yearly trend. Am I the only one?1
-
But why can’t Android Studio work out of the box?
I want to develop, Not mixture with gradle and stuff...
Time for a Power Nap.2 -
Android Studio and Gradle -- because sometimes you just need to practice unplugging your computer.1
-
Heck yeah,
So an old Ionic 3 project wont work on the newest CLI.
I check around for the error, update some dependencies, sure enough it starts working again, all is great or so I thought.
Later something weird starts happening, upon pushing a new view on the navCtrl, the navParams are null on the next view.
I later find out that navCtrl is becoming navParams just on the first bit of the view loading, so I do a dirty fix just to keep working on the functionality from my browser, I know very well this will cause problems later on, this is just so I can keep working on functionality.
I finish all of the functionality and I'm ready to compile for android, I run my script, the dirty fix comes to bite my butt now.
I remove the dirty fix hoping for it to work just well on the apk.
Now gradle doesn't find ddmlib.jar, some 15 minutes of troubleshooting do nothing.
Fuck it, I'll just create a new project from the CLI and drag all the code there so that navParams work as expected.
Sorry Ionic, but the world is not our oyster when subtle changes in dependencies produce such unexpected behaviour, with some fucking view parameters!.
I'm looking forward to get done with all the current projects to jump back to native.1 -
gradle is infuriating.
firstly there are so limited resources to understand how it's building a java/android code. everything happens by magic and hit+trial
secondly the plugins and the tasks works in mysterious ways. sometime they work when applied in the project root's gradle file, other times they work when applied in module's gradle file, nd other times they need configuration at both levels.
then there are gradle tasks like build ,test, assemble , clean etc. these are less of an action and more of an alias to run a bundle of actions.
then we have 3rd party plugins which attach themselves to these "fat-actions" and run before/after them
and finally we have the fuckup from the java world where the only available code coverage plugin is jacoco and IT FUCKING SUCKS!!! it is a test environment plugin, it should impact test tasks , but somehow it's fucking with the assemble taskin such a manner, that the jars ans aar files generated via plugin are giving runtime errrors. yes , runtime! as if we are back in the messed up js world of "everything is good unless running live"
even if it was a compile time eeror, i would have considered. but runtime?!! fucking runtime error?! i barely understand this shit, there is absolutely no info available as to which classes are being used to create a build and how, and i am supposed to fix this? wtf?!4 -
Android Studio the most complex software i have ever used!!
Gradle build!!
Helps me in winter and keeps me warm 😅😅😅 -
I started with my first Android project. Here are some of my observations.
Turning of fossil into fuel - 650 million years
Transformation of a star into supernova - 10 billion years
Complete gradle build - fuckzillion years2 -
I'm really fed up working with android studio.
I had to use it on my vocational training. I had lubuntu there, and we weren't allowed to bring along our own laptops. In my desktop I had ubuntu and windows 7.
I had to work with my project made in lubuntu at home, and it didn't work, on neither OS. I eventually tested I wasn't able to run the project cross plataform thanks to my desktop, but when I installed android studio on my laptop, it seems like it doesn't work with the same OS but a slightly (one week) version later.
I had to scrap the whole project on my desktop, copy the laptop's installer into desktop's window and make it all over again in order to be able to use the same project in both of them.... Until I updated. I updated both of them without reinstalling them, and the gradle never agreed again.
After two years I'm trying again and this problem still exists... And gradle is now even slower to crash. -
I FUCKING HACK ANDROID DEVELOPERS SERVER IF THIS SHIT DOES NOT WORK I HAVE BEEN LITERALLY WAITING IN THIS STATE FOR AN FUCKING HOUR.
STOP IT.
STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.STOP IT.PLEEEEEEEASE11 -
Gradle,Android Studio
Boss: Great job can we change the UI by using a custom view..
Me:Hesitating a bit sure we can.Head back to my station and consult Stack overflow and start implementing.
Boss:Five minutes later you done and how is it so far.
Me:Am done am just rebuilding and cleaning my project yet in reality ain't done.Gradle built time to my rescue.
Boss:How comes it taking long yet you got a high end machine okay then let it built.
Me: Breathing a sigh of relief thanks gradle1 -
Working on a project.
New gradle update comes out.
Updates his gradle.
Nothing works anymore!
Moral of the story.
This is why you should mind your own business. -
Dafuq is wrong with Android Studio, build error report is useless every time I have error in one of my files I need to run gradle assemble debug manually to know where the fuck is my error
Like now I changed type of a property and as usual build report showed error in Databinding auto generated class instead of pointing to my fragment where the error should be3 -
Client: How many days do you need for this project
Me: 6 months
Client: That's too much. I researched and found that it shouldn't consume more than 3 months
Me: I'm sure you didn't researched on gradle building process (-_-) -
Hey Android Studio when I put you to bed you was happy and we had so much fun! Why in the morning when I open my project you complain about build issues? What changed?...
Oh, I get it GRADLE is messing you up again! FMDL2 -
Everytime I go back to native Android, I end up: -Wasting a lot of hours with gradle and the shitty dependency system.
-Doing a couple of cours of actual coding and finishing what I needed to do.
-Swearing to never come back5 -
Ok, so I'm a student and in my free time, I mostly write a bit of python, C++ and a bit Haskell for fun...
I wanted to try out Android development now...
HOLY FUCKETY FUCK, THIS SHIT TAKES TIME!
most of the time, I get an idea, open vscode and start typing (maybe install some modules for like 10 minutes), not with this: Android studio took hours to download with all the needed SDKs and libraries, then I created a new empty(!) Activity, then fucking Gradle needs hours to get it fucking ready... On a fucking XPS 13 9370!
How do you guys cope with that waiting, does it scale that way to bigger projects?
I would call myself rather patient, but if I have an idea, I don't want to set up the most basic environment for 3 hours...
Man that shit is bulky...4 -
I updated NDK, which resulted in some critical errors, because of outdated Gradle used deprecated NDK features.
I read about it, and decided to fix it properly, not hacking around - updatig that old gradle 2.2 to 4.10.2.
I spend about 6 hours fixing all problems and warnings that gradle had because of that, and then some.
At the end, some things still didn't work, but i was clearly missing some code from version control. I clicked update and left it for an hour.
THIS FREAKING BUGGY TFS PLUGIN RUINED ALL MY FILES I N THE PROJECT. WHY ARE WE STILL USING THAT F*King TFS???
Literally, I'm left now with .iml files in folders.
And my updated gradle files are gone too. -
Oh Good job you fucking gradle and InteliJ that telling me the specific fucking error you pice of shits.
-
I'm about to start learning Android development. First it's the obligatory Get Started, then a couple of Udemy courses. After doing javascript for so long, i think it'll be nice to use a strongly typed language again (Java is my first language; college you know).
But, I'm REALLY not looking forward to Gradle wasting my time--it took two minutes to even start up the IDE for the initial project.
Ah well, nothing's perfect3 -
FOR FUCKING FUCK SAKE
I have a shit ton work to do. Just finished (hopefully) all of my exams, came back to work and got tasked with simultaneously developing a new app (Android), adjusting some of my own code to work with client's specific requirements in completely different project (C#) and also I have to fix a legacy app (Android) because UE comitee will be visiting us on wendesday.
I've never seen this code earlier. I've never seen this WHOLE SHITTY PROJECT. Guy that was developing this left few years back.
It's a complete spaghetti. 550 FUCKING LINES OF CODE for a one class, most of the methods are deprecated and won't even try to work on Android > 4.0. No documentation. Nothing works. Whole code is ridden with bugs, warnings and looks like it's glued together with duct tape. I even had to migrate from fucking Maven to Gradle it's that old. -
I still hate Android Studio :( :( :(
Worked all morning on my project, debugging, no problem.
Now all of a sudden it crashes whenever I try to debug. java.lang.ClassNotFoundException - random classes.
But it runs fine if I just run the app.
I reverted to my last working commit, and it still does that. I restarted my computer. No luck.
I disabled Instant Run. No luck.
I tried to upgrade gradle to 3.3 - no luck. That's the extent of stack overflow suggestions for similar errors.
I am stumped. What has changed in the middle of a work-session when I have not changed any settings in the IDE, have not updated anything.
Aaarrgh!6 -
🤤🤤🤤I seriously just spent the whole day trying to fix something that looked like it was ProGuards fault, but it turns out fuckimg Gradle plugin and android studio shat all over every version of every project on my home.
Literally 15 hours wasted.
Defeated in an Uber going back home direct to bed with only a single meal today
Tomorrow can't go worse I guess.
At least I get that going for me.
Hope your day was better -
I'm developing Android apps for my pastime (student on summer break) and will use my phone for running/debugging apps because my shitty laptop can't run the emulator.
If receive a call when I'm using the phone for debugging, I'm not picking it up. Even if it's a friend with whom I've not spoken in weeks. That call has to wait for my gradle to finish building.
Of course, I try to call back as soon as possible but that sometimes means an hour or two when I decide to get up from my laptop.
I'm not sorry8 -
So, I have a pretty decent understanding of big complete languages like Java, I build android applications following several design patterns, solid principles, building big stuff with databases and servers and libraries interconnected with gradle, tracking everything with git, using tdd and functional programming capabilities blablabla ... And I still have trouble making sense of a FREAKING STUPID SHELL SCRIPT I MEAN WHO CAME UP WITH THAT SINTAX I HATE IT SO MUCH OMG I CAN'T EVEN
But for real everytime I need to read a '.sh' I literally wanna throw my computer away and die. Am I alone? -
!rant
Buying a new laptop here
Is i7 worth the money or i5 more than enough? Both 6th generation
Mostly will be used for android development
(Gradle is hell 😂😂)13 -
When I moved to another company there was Android app, with 5K lines of HTTP Service class, with apache legacy library, with maven and tons of garbage.
now, it has gradle, multiple build types, flavors, multiple source sets, RxJava, Java 8, ButterKnife, modular dependency, I always do profiling and APK analyze and tons of essential and cool features.
Project started last year but what the heck?
Dude, I will find you,and I will kill you! -
What is wrong with Android Studio it used to be better just the sheer number of updates and the gradle build oh the gradle build5
-
Today I made some tests with flutter, I really liked it :)
What I didn't like was the time that Android studio takes to load, the memory it uses, and the time of gradle builds. I'll be using nvim, so, half of the problems are solved.2 -
My favorite tools include:
Source tree(git life saver)
Stickies on my dock(I can randomly put any shit on it and keep it for months)
Android studio(love shorcuts except gradle)
My moto x smartphone (helps me in debugging) -
so my poor old hp bro is starting to give up on me after 3 years . there are both battery and performance issues. I knew its death was near when i got its keyboard replaced i saw its battery's state 6 months ago. it was fat as me . Now it can't live without the wire for more than 30 mins.
apart from that am getting frustrated with everyday performance of my system. all i open is 50 tabs of chrome and android studio where bitch gradle generates a billion byte sized files at million places and cache folders . (and sometimes a terminal and/or files and/or vscode).
I have decent specs tho i5 7th generation/8gb ddr4 ram/ 2gb nvidea graphics/ 1tb hdd. but still my ubuntu gets stuck everytime i switch between chrome and AS . (maybe i have not made correct swap partitions or maybe there is an issue due to ubuntu/windows dualboot)
what should i do ? I guess i have to spend some shit on a new battery. But apart from that, iwanted to know about performance. how to get a beter performance?
I have heard of solutions like getting an sdd or increasing ram, but am broke af and might not afford a 1tb ssd (yes i do need that much amount of memory, my system is currently at 650 something gb) and about ram i have heard it doesn't offer much improvements. is that true?What should i do?6 -
Been working on an Android app for some time. Silly me too lazy to use VCS. Anyway, one day android studio just could not build my project and errors that should not be errors popped up everywhere and nothing I did fixed the problem. Somehow my project got corrupted. 3 hours later of googling and trying to recover my project I had to resort to creating a new project and manually port the old files in one by one :( but all I have to say is WHAT THE FUCK ANDROID STUDIO3
-
I have tried so hard to add some dependencies on react-native (android). Always fails when build gradle, many dependencies are mismatch.
Go fuck my project.2 -
fuck gradle
i have dependency tree like this
±--com.vincent.filepicker:MultiTypeFilePicker:1.0.5
±--com.github.bumptech.glide:glide:3.7.0 -> 4.3.1
±--com.github.bumptech.glide:glide:4.3.1 (*)
glide.3.7.0 as transitive dependency got fucking overridden by glide:4.3.1 how do i fucking keep glide:3.7.0 from getting overridden, been search for a day and no solution worked, fuck gradle how come shit like this doesnt have straight forward solution ?3 -
In morning I thought to complete my work asap so I quickly went to office, started my laptop
....... after few mins it started.
I clicked on Android Studio Launcher......................................................................................................................................................................................................................................... (after 15 mins) it started.
I clicked on the project to load..........................................................................................................................................................................................................................................................gradle is building message................................................................................................................build.gradle message..................................................................................................................after 30 mins it loaded.
Finally I did some code, made some UI changes in layouts and clicked on RUN :(
............................................................................................................................................10 mins.......................................... another 10 mins.............................................................................................. after 28 mins it ran on my device. At this moment I couldn't think to start emulator..
In the end I couldn't complete my work.5 -
This cunt android studio, asshole. Every fucking day it would show me a pop up saying, "hey, update gradle", I always ignored it until today and that mofo has fucked up my project. Spent last 3 hours debugging as to why it is not able to resolve dependencies which were working fine earlier. And every time I click on "try again" it will resolve the dependency which it wasn't able to earlier but instead find a new one to fuck with and throw an error. Had to come back to old version resume my work FFS.2
-
Working with windows and android studio makes you sitting crying in firnt of you laptop, repeatedly singing "i hate you i love you"
And obviously if you are googling what makes android studio so slow( not while gradle crap builds!) some people also write that android studio has no problem on linux. Fuck7 -
Either I missed it in the docs or Google actually changed it, spent 15 minutes trying to figure out why my app isn't building and why build log is not showing anything other than: Build failed
Until I manually ran gradle build process instead of making Android studio execute it.
Am I missing something? .-. -
So, I have multiple modules, each has build.gradle file. Why is it everytime I run, it refreshes all indexes and doing grail build run?1
-
It's not often that I wonder whether Software Development was the wrong career choice. But when I do have these thoughts, it usually comes after struggling with Gradle.
-
Ugh Android OS is so vast and intimidating, i feel so unsure about it even after 3 years of learning it.
Like now i am about to graduate, so i need to look for a job. Those companies require knowledge of libraries like data binding, dagger, rx fabric, etc the stuff that i never personally used in any of my personal projects because i was able to handle all my stuff by general programming knowledge.
At the same time the os itself is so large and full of apis that i want to learn and spend my time upon. Like Android stores data, renddrs media , its databases, its lifecycles, gradle building , manifest etc
Can any devs share how they are proceeding with this os? I always feel like i am floating on the surface and not diving deep enough :/2 -
Took me 2 days and a fuckton of googling to successfully sync my first android project with this thing called gradle
But well, I can finally say hello android world!1 -
What the ****? I added a call to one method, how the hell it could broke it so badly?
> Compile failed with 1163 errors; see the compiler error output for details.1 -
Firebase api is good simple and alright but when you want to add it to your android project , you want TO KILL YOURSELF. OK first gradle works then say oh you should update your gradle you update it . then it says cannot resolve firebase:core WHaaaaT? OK YOU SEARCH FIREBASE API FOR AN ANSWER THERE IS NOTHING THERE. then stack overflow come to your help you should update some FUCKING package that firebase didnot mention you should update and all this time you say dns is wrong , firebase is filtered your country again, and after you update thise tow package you found out that you should update your android studio too for just one line code(firebase mentioned this but I said noooo it's just optional) .2
-
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! >:( -
so am switching jobs as an Android dev from a company which made android libs (using almost 0 external dependencies and mostly java) to a company which makes android apps( and is probably using either rx/guava/ribs/hilt etc or the more fancy hilt/compose/coroutines/clean-arc etc. its either one of them depending upon the maturity of product)
B2C folks use tons of libraries in favor of delivering fast but learning about those libraries while taking new tasks and fixing bugs CAUSED by those libraries ( or their inappropriate usage) is a big PAIN IN THE FUCKING ASS.
I remember i had once became such a weird dev coz of my prev company ( before the current libraries one, which was also a B2C) .
on weekends i would come up with a nice app idea, start a new android studio project, and before writing a single line of useful code, i would add a bunch of libraries, gradle scripts and extensions .
that ocd will only settle once all the steps are done and i can see a working app after which i would write the code for actual code for feature implementation.
granted that these libs are good for creating robust scalable code, but most of the times those infinite kayers of seperation, inheritance and abstraction are not really needed for a simple , working product.
:/
i have also started reading about rxjava , and although i am repulsive to this library due to its complicated black box like structure, i find its vast number of operators nd built in solutions very cool.
at the end of the day, all i want is to write code that is good enough for monkeys, get it shipped without any objections and go back home.
and when you work on a codebase that has these complicated libs, you bet your ass that there will be thos leetcode bros and library lover senëõr devs waiting to delay the "go back home" part 😪2 -
Ahhh!!! Stupid ass Android studio taking abt 5 mins for initial build AMD throwing out tricking gradle errors which take up 45 mins to fix
Someone throw it in a river of piranhas already!!1 -
Today, I installed Android studio on my macAir with virtual emulator without any Gradle failed things. Had so many problems when i did it on my windows and linux laptop :/. Today i just clicked next next and done :/. Mac is ❤
-
Where is the mac vs ubuntu vs windows war for developers? I am a Windows user (on a dell latitude e5570), but I am considering a new laptop because everyone says macbooks are great and outperform windows (which on gradle builds is true).
I mainly use my laptop only for developing and programming things like: full-stack, Android and a little bit of deeplearning/ML.
So which one would you recommend and why? These are pretty heavy tasks, from my opinion.10 -
when you get married after you start a gradle build, and then the build finishes 5 years into the marriage and you get divorced bc the software idea was garbage anyway ¯\_(ツ)_/¯
-
Dear android devlopers, do u suggest me to upgrade to androidx ? Or stick with the working support libraries ?
Im effraid to upgrade and dive into dependencies hell1 -
Maybe it just me, but I am tell to myself with confidences "I am smart" when I figuring out how to make GRADLE work offline.
But then I hit 'make project' I find failed linking reference.
I am yelling to myself "why in the hell I still working with these stuff anymore!"
"Gradle sync offline" with gradle is fine, then I find another boss battle "Gradle build offline" -
I love linux because i dont have to forced to do frickin update like windows did.
Because i have an experience after update linux mint i cant even start the main GUI program. After boot only show blank console. It seem linux update broke the compatibility between my graphics card.
At least now i dont have to update because thats an option. The output of update is not different than windows.there is a chance you broke your OS.
But the struggle is when i need to install new app in linux. Sometimes need more than hour to find out why it doesnt work from the first time.
Any help here?
So this start from the office. In the office i usually use low spec laptop that work slowly. Then i found this IDE called rapidclipse. Its very promising with GUI builder and can build cross platform mobile app using only java built on top vaadin framework.
When i use it on low spec laptop hackintosh at office it work well although it take more time than other kind of eclipse and i dont need to install any kind of app again, just download-install-create new project-run on tomcat-work well.
Then i go to home to try this new tool , IMO my low spec PC still have more power to run something than old hackintosh. Because usually i use android studio with no problem. In the old hackintosh it went too long to build gradle only.
Then i install rapidclipse, then run desktop shortcut. Then it said i need to install correct java to use correct JavaFX.
After search on SO they said i must install jdk from oracle.
Ok so i got openjdk in my linux.wtf what is the different idk but dont have time to find out.
I install jdk from oracle.
Than finally can open the rapidclipse.
Wow , this gonna be fun.
Then create new project. Just a new project.
So im waiting. I see the progress at 10%. But still no increment on that.
I switch to other app for several minutes.
Then when switched back th app still at 10% and now is at no responding state. So i force close.
After that open rapidclipse again.
The previous new project can be opened. Yay, i think.
But so many error there. Omg.
So i create new project again.
But, but, i just repeated the first error then close again then try it again for several time. But still same output.
After an hour, i give up.
But still, why , just why it work like this. No error or whatsoever.
Back later i have a problem like this on different app.
Idkwhy.1