The plugins block is the newer method of applying plugins, and they must be available in the Gradle plugin repository. The apply approach is the older, yet more flexible method of adding a plugin to your build. The new plugins method does not work in multi-project configurations (subprojects, allprojects), but will work on the build … Read more
I updated my Android Studio to 2.3 and it asked me to update my gradle plugin to 3.3 that created issues with my running projects. I’ve gone through all the Stack solutions and nothing worked for me except this workaround: I changed my distribution url in gradle-wrapper.properties with this one. distributionUrl=https\://services.gradle.org/distributions/gradle-5.6.2-all.zip (permanent link list here … Read more
I had similar problem. Added two lines in gradle.properties file: android.useAndroidX=true android.enableJetifier=true These two lines automatically resolved my dependency conflicts between google’s files and third party dependencies. Here’s the link to follow: https://developer.android.com/topic/libraries/support-library/androidx-overview#new-project
tl;dr Just replace: compile with implementation (if you don’t need transitivity) or api (if you need transitivity) testCompile with testImplementation debugCompile with debugImplementation androidTestCompile with androidTestImplementation compileOnly is still valid. It was added in 3.0 to replace provided and not compile. (provided introduced when Gradle didn’t have a configuration name for that use-case and named … Read more