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
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
No cached version of org.ow2.asm:asm:5.1 available for offline mode.
Disable Gradle 'offline mode' and sync project
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.
This sort of compatibility breaking was fairly common back in the AS 1.X/early 2.X days. As of now, it's really rare, and usually resolves automatically.
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)
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.