Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Android Studio 3.1 Stable

android-developers.googleblog.com

Post reply on HN
Print view View original

31–40 of 43 posts

Re: Android Studio 3.1 Stable

#31

Post by V-2 »

pjmlp wrote: post #27
mundanevoice wrote: post #25

Earlier quoted context omitted.

Okay. That's almost crazy. In my almost 3 years of maintaining our app that was originally written in Eclipse, we never had to face any single issues like this. There were some minor issues but never like this. It makes me wonder if the your project structure or the way project is written is crappy.

Well, just spend some time reading Android developer forums on Reddit, G+ or Google groups, every time there are new SDK or Studio stable releases. The dheera is not alone.

Well, yes, it always happens to someone - I mean, every upgrade will break some stuff for some devs. After all, the userbase of Android Studio is quite sizeable.

What I find hard to believe is that these problems would hit the same bunch of people every time, and on the top of it, affecting every project they work on. Come on.

And this is what dheera claimed ("almost every release of Android Studio has succeeded in breaking every single Android app"). If it's really so extreme, I'd say that he - or she - is not unlikely to be alone, or close to that.

Re: Android Studio 3.1 Stable

#32

Post by V-2 »

realharo wrote: post #24
clumsysmurf wrote: post #4

Android Studio has such a fat ass. Every release it, and gradle, want more memory to do the same thing. I'm hoping that the tools devs improve or review the resource usage of the gradle plugin, etc. VS Code and the flutter tooling are svelte in comparison.

To be honest, everything about Android seems like a bit of a mess to me - the APIs, the tools, plus all the things from the user's perspective.

Yes it's a dirty world overall, but Android Studio - all its issues notwithstanding - is a great improvement over Eclipse regardless, and an awesome IDE. At least in terms of software design as such.

Re: Android Studio 3.1 Stable

#33

Post by kuschku »

V-2 wrote: post #31
pjmlp wrote: post #27

Earlier quoted context omitted.

Well, just spend some time reading Android developer forums on Reddit, G+ or Google groups, every time there are new SDK or Studio stable releases. The dheera is not alone.

Well, yes, it always happens to someone - I mean, every upgrade will break some stuff for some devs. After all, the userbase of Android Studio is quite sizeable. What I find hard to believe is that these problems would hit the same bunch of people every time, and on the top of it, affecting every project they work on. Come on. And this is what dheera claimed ( "almost every release of Android Studio has succeeded in…

The crazy part is, while I have the same issues with every release of Android Studio – the same project in IDEA works just fine, without any trouble, ever.

In fact, JetBrains quality and reliability has been much higher than the piece of shit IDE Google has been producing.

Re: Android Studio 3.1 Stable

#34

Post by dep_b »

satysin wrote: post #22

I am surprised Google have not acquired JetBrains by now. Android Studio being based on their IntelliJ platform and Kotlin getting first class support in Android is investing a hell of a lot in a relatively small foreign company. Kinda strange as Google have acquired larger companies for less (less reliance not value).

If I trust any company with JetBrains it would be Microsoft. But they already have top notch products...I'm using PyCharm and Visual Studio Code side by side now and it's like VSC has like 10% of the menu options yet does everything I want it to do. Something like macOS versus Windows in terms of simplicity vs features.

Re: Android Studio 3.1 Stable

#35

Post by sankalp_sans »

barbs wrote: post #21
dheera wrote: post #16

Earlier quoted context omitted.

Almost every release of Android Studio has succeeded in breaking every single Android app I wrote. I have always had to cut and paste every class, resource, layout, one by one into a new project in order to get it to compile. I always fear pressing the "update" button.

What kind of ridiculous project structure do you have? I have never in my ~5 or so years of using Android Studio have had to do something as drastic as that. I have occasionally have had issues with updating, but this has required a tweak in the gradle file and an update of build tools, at most.

> What kind of ridiculous project structure do you have?

Obviously one that was supported in every preceding version of Android Studio. When making consumer-facing tools, it is the job of the tool maker to make sure that it doesn't break.

If something works in a version, and breaks in another, guess who is to be blamed? (hint: not the user)

Re: Android Studio 3.1 Stable

#36

Post by dheera »

barbs wrote: post #21
dheera wrote: post #16

Earlier quoted context omitted.

Almost every release of Android Studio has succeeded in breaking every single Android app I wrote. I have always had to cut and paste every class, resource, layout, one by one into a new project in order to get it to compile. I always fear pressing the "update" button.

What kind of ridiculous project structure do you have? I have never in my ~5 or so years of using Android Studio have had to do something as drastic as that. I have occasionally have had issues with updating, but this has required a tweak in the gradle file and an update of build tools, at most.

Let's see, I just upgraded to Android Studio 3.1, opened one of my previous ridiculously simple apps, and voila:

    Could not find com.android.tools.build:gradle:3.0.1.
    Searched in the following locations:
        https://jcenter.bintray.com/com/android/tools/build/gradle/3.0.1/gradle-3.0.1.pom
        https://jcenter.bintray.com/com/android/tools/build/gradle/3.0.1/gradle-3.0.1.jar
    Required by:
        project :
    Add Google Maven repository and sync project
    Open File
Okay, I hit the "Add Google Maven repository and sync project", and now we have:

    Could not GET 'https://jcenter.bintray.com/org/ow2/asm/asm/5.1/asm-5.1.pom'. Received status code 502 from server: Bad Gateway
    Enable Gradle 'offline mode' and sync project
I don't know what the hell any of this means -- I'm not a Java/Gradle/etc. person at all, just forced to use this pile of mess for Android -- so I cluelessly hit "Enable Gradle 'offline mode' and sync project" hoping it will resolve the error, and now:

    No cached version of org.ow2.asm:asm:5.1 available for offline mode.
    Disable Gradle 'offline mode' and sync project
Created a new project and it compiled successfully. Cut-and-paste classes, here we come!

On another note, creating a blank Android app results in nothing short of 87 files. Does it really have to be this complicated? Do we really have to use this gradle nonsense? (90%+ of the errors I get hen upgrading Android Studio say something about gradle). Most frameworks on other platforms are simple and elegant enough that it is possible to memorize the minimal "hello world" example and implement it with vim, and the IDE is just there for convenience, not out of necessity.

Re: Android Studio 3.1 Stable

#37

Post by seviu »

dheera wrote: post #36
barbs wrote: post #21

Earlier quoted context omitted.

What kind of ridiculous project structure do you have? I have never in my ~5 or so years of using Android Studio have had to do something as drastic as that. I have occasionally have had issues with updating, but this has required a tweak in the gradle file and an update of build tools, at most.

Let's see, I just upgraded to Android Studio 3.1, opened one of my previous ridiculously simple apps, and voila: Could not find com.android.tools.build:gradle:3.0.1. Searched in the following locations: https://jcenter.bintray.com/com/android/tools/build/gradle/3.0.1/gradle-3.0.1.pom https://jcenter.bintray.com/com/android/tools/build/gradle/3.0.1/gradle-3.0.1.jar Required by: project : Add Google Maven repository an…

Bintray is having major outages today. That explains the 502

Re: Android Studio 3.1 Stable

#39

Post by CodeWriter23 »

cseelus wrote: post #38

Has anyone here worked with 3.1 as well as Xcode and can say something about the simulator experience of Android Studio?

I’m an iPhone and Mac user. Can’t say I gave the Android emulator a good chance for me to like it. But just a couple of tries had me reaching for the Samsung J30 I picked up for on-device debugging. The emulator was pretty slow is why. Sounds like they worked on that for 3.1 though.

Re: Android Studio 3.1 Stable

#40

Post by CodeWriter23 »

satysin wrote: post #22

I am surprised Google have not acquired JetBrains by now. Android Studio being based on their IntelliJ platform and Kotlin getting first class support in Android is investing a hell of a lot in a relatively small foreign company. Kinda strange as Google have acquired larger companies for less (less reliance not value).

Google seems to often kill the great products they acquire.
Post reply on HN