4 ms·

I love Intellij but Android Studio so far was a complete constant disaster. Obscure build errors, very slow builds, all kinds of device connection failures, gr

• singularity2001 9y ago
  Session 'app': Error Launching activity not much has changed :( I know, the above bug can be circumvented by unchecking "Instant Run"
  • singularity2001 9y ago
    Installation failed with message Failed to install all . That's enough for today OK, just one more: Error while uploading slice_4.apk : java.lang.UnsatisfiedLinkError: No implementation found for java.lang.String android.os.SystemProperties.native_get(java.lang.String)
    • heartbreak 9y ago
      This series perfectly sums up my experience with Android Studio. IntelliJ itself, on the other hand, works every time.
      • pjmlp 9y ago
        I always wonder how they actually test it. Last RC did not even update on Macs.
  • jakub_g 9y ago
    "Error Launching activity" depends a lot on the device. For example it happens a lot for me on a Moto G3 but rarely on HTC. Are slow builds AS-specific? I think it's more related to the Android build ecosystem and not the IDE.
• arvinsim 9y ago
  I feel this is less on Jetbrain's IDE and more on the Android environment.
• pjmlp 9y ago
  After my experience with Android Studio I started to enjoy using Eclipse again. The migration experience was even worse for those of us using the NDK. Three reboots for the build system, no migration path until CLion was developed, debugging features only available to Java code,... Although they have made major improvements, I always ask myself if they had spent all that money improving the Eclipse based IDE, how much better the overall experience would be.
  • stuaxo 9y ago
    This is what the android build system has been like since way before Android Studio - there are always incompatibilities between versions.
• jayd16 9y ago
  You pretty much just listed gradle 4 times.
  • kuschku 9y ago
    Except, Gradle 4.1 with kotlin scripts (unless android studio overwrites your gradle version AGAIN) works fine nowadays. But Android Studio actually managed to break builds on non-US locales because they used String.format using the system locale (which means %02.f renders with a ,)
• yummy 9y ago
  It has nothing to do with JetBrains. You won't find it on their website
  • Wehrdo 9y ago
    The core of Android Studio is IntelliJ.
• joelhaasnoot 9y ago
  Isn't this true of mostly any dev environment? You'll run into one or more of those every once in a while. Colleagues running XCode for iOS development think it and Swift are a piece of crap too most of the time (though the latest rewrite for iOS 11 apparently was a big improvement). I've ran this version for going on 3 months now and pretty happy. I've run into some issues with Kotlin builds and preprocessors (can't see the build errors in the Gradle console, have to run a command line build with --debug flag) and every once in a while the emulator and IDE stop talking with each other (ADB needs a reset every so often).
  • com2kid 9y ago
    > Isn't this true of mostly any dev environment? C# + Visual Studio, the build will just work. The fact that editing the MSBuild XML is not really necessary for 90% of developers helps with this a lot.
    • joelhaasnoot 9y ago
      You're probably right for modern/default use cases, but I've seen C++ for Windows Mobile fail terribly too (Android Studio supports NDK/Native C++ code also).
• derptron 9y ago
  How subjective. I've been using AS for 2 years without any major issues that weren't my own fault.