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 ,)
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).
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.
not much has changed :(
I know, the above bug can be circumvented by unchecking "Instant Run"
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)
Last RC did not even update on Macs.
Are slow builds AS-specific? I think it's more related to the Android build ecosystem and not the IDE.
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.
Obscure build errors, very slow builds, all kinds of device connection failures, gradle wtfs, (un)necessary manual config edits .....