Could not resolve com.android.tools.build.gradle:3.0.1

Question

I'm forcing gradle to use http I have modified my gradle-wrapper.properties:

distributionUrl=http\://services.gradle.org/distributions/gradle-4.3-all.zip

The build.gradle:

buildscript {
repositories {
    //jcenter()
    //google()
    maven { url "http://jcenter.bintray.com"}     
    }
dependencies {
    classpath 'com.android.tools.build:gradle:3.0.1'

    // NOTE: Do not place your application dependencies here; they belong
    // in the individual module build.gradle files
}}

allprojects {
repositories {
    jcenter()
    maven { url 'http://maven.google.com' }
    maven { url "http://jitpack.io" }
}}

As far as I'm aware I should use 3.0.1 but when I check the actual repo on jitpack or maven only up to 2.3.3 is available.

The error message I'm getting is:

> Could not resolve all files for configuration ':classpath'.
> Could not find com.android.tools.build:gradle:3.0.1.
Searched in the following locations:
http://jcenter.bintray.com/com/android/tools/build/gradle/3.0.1/gradle-3.0.1.pom
http://jcenter.bintray.com/com/android/tools/build/gradle/3.0.1/gradle-3.0.1.jar
Required by:
     project :* Try:

Gradle version is 4.3.1 JVM 9.0.1

What can be done to successfully run 'gradle test' here?

EDIT: uncommenting //google() reveled:

       > Could not get resource 'https://dl.google.com/dl/android/maven2/com/android/tools/build/gradle/3.0.1/gradle-3.0.1.pom'.
        > Could not GET 'https://dl.google.com/dl/android/maven2/com/android/tools/build/gradle/3.0.1/gradle-3.0.1.pom'.

When modified the http repo

buildscript {
repositories {
    //jcenter()
    //google()
    maven { url "http://jcenter.bintray.com"}
    maven { url "http://maven.google.com"}

    }

I got:

      > Could not resolve com.android.tools.build:gradle:3.0.1.
     > Could not get resource 'https://dl.google.com/dl/android/maven2/com/android/tools/build/gradle/3.0.1/gradle-3.0.1.pom'.
        > Could not GET 'https://dl.google.com/dl/android/maven2/com/android/tools/build/gradle/3.0.1/gradle-3.0.1.pom'.
           > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
  > Could not resolve com.android.tools.build:gradle:3.0.1.
     > Could not get resource 'http://maven.google.com/com/android/tools/build/gradle/3.0.1/gradle-3.0.1.pom'.
        > Could not GET 'http://maven.google.com/com/android/tools/build/gradle/3.0.1/gradle-3.0.1.pom'.
           > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

I get the same if I uncomment both jcenter() and google(). Besides, when I check https://dl.google.com/dl/android/maven2/com/android/tools/build/gradle/ the link is dead. Now the jcenter repo https://repo1.maven.org/maven2/com/android/tools/build/gradle/ ends on 2.3.3 version which seems to be correct that this error is happening, the question is what is wrong then?

EDIT- Likely solution the issue happenned because you can't run those excluding https completely, it will fail either way.

Check this [link](https://developer.android.com/studio/releases/gradle-plugin.html) your android studio must compatible with gradle version — yashkal, Jan 16 '18 at 08:29
ok although this is not in android studio but in the command line. I'll uncomment it — kol23, Jan 16 '18 at 08:34
If @Omi 's advice won't help try to uncomment //jcenter as well. — AloDev, Jan 16 '18 at 08:37
just tried as the below answer by IntelliJ Amiya suggested, Getting the same > Could not get resource 'http://maven.google.com/com/android/tools/build/gradle/3.0.1/gradle-3.0.1.pom'. — kol23, Jan 16 '18 at 08:43
There must be a problem with some kind of proxy. Check this out: https://intellij-support.jetbrains.com/hc/en-us/community/posts/115000094584/comments/115000405564 — R. Zagórski, Mar 08 '18 at 16:29
try adding google() to allprojects.repositories while uncommenting also in the buildscript.repositories and remove the maven dependencies — emirua, Mar 09 '18 at 00:03
You're last stack trace is stating that `dl.google.com` is not a trusted host, but that can't be unless if a certain proxy is doing some SSL offloading on behalf of it and providing a fake SSL certificate when undergoing the handshake. If your unaware of a proxy please be careful as this could mean a man in the middle attack. With regards to the repo's, all of them seem to provide the artifacts over https and no loner http any more, try jitpack for example it will always redirect http to https. — ahasbini, Mar 15 '18 at 00:09
are you on company's network. Because most of the company's firewall is blocking this. — KKSINGLA, Mar 15 '18 at 06:00
in your gradle properties add this `android.enableAapt2=false` — Hemant Parmar, Mar 15 '18 at 11:08
use this link https://stackoverflow.com/questions/51797446/android-studio-3-1-4-gradle-sync-failed — Engineer Rasul Shamohamadi, Apr 05 '19 at 16:36

IntelliJ Amiya · Answer 1 · 2018-03-12T05:46:07.947

8

Could not resolve com.android.tools.build:gradle:3.0.1.

Read Google's Maven repository

Include Google's Maven repository in your top-level build.gradle file:

FYI

allprojects {
    repositories {
        google()

        // If you're using a version of Gradle lower than 4.1, you must instead use:
        // maven {
        //     url 'https://maven.google.com'
        // }
        // An alternative URL is 'https://dl.google.com/dl/android/maven2/'
    }
}

So, According to your version your build.gradle will

buildscript 
{

    repositories {
        jcenter()
        google()
        maven { url "http://jcenter.bintray.com"}     
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.0.1'

    }
}

allprojects 
{
    repositories {
        jcenter()
        maven { url "https://jitpack.io" }
        google()
    }
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

edited Mar 12 '18 at 05:46

answered Jan 16 '18 at 08:37

IntelliJ Amiya

74,896
15
165
198

I have edited my answer, tried this exact setup and produced the same error, Could not get resource 'https://dl.google.com/dl/android/maven2/com/android/tools/build/gradle/3.0.1/gradle-3.0.1.pom'. – kol23 Jan 16 '18 at 08:41
@koller23 Kindly Restart IDE and gradle – IntelliJ Amiya Jan 16 '18 at 08:46
Besides I can't use https this time, Regarding IDE this is only command line like gradle test, fastlane test etc. – kol23 Jan 16 '18 at 08:46
1

@koller23 add `allprojects { repositories { jcenter() maven { url "https://jitpack.io" } maven { url 'https://maven.google.com/' } google() } }` – IntelliJ Amiya Jan 16 '18 at 08:55
I can't use https. Tried http. After stopping gradle daemon and adding the above > Could not resolve all files for configuration ':classpath'. > Could not find com.android.tools.build:gradle:3.0.1. Searched in the following locations: http://jcenter.bintray.com/com/android/tools/build/gradle/3.0.1/gradle-3.0.1.pom http://jcenter.bintray.com/com/android/tools/build/gradle/3.0.1/gradle-3.0.1.jar – kol23 Jan 16 '18 at 08:59
@koller23 Kindly check this link https://stackoverflow.com/questions/47515676/gradle-4-1-issue-on-latest-android-studio-3-0-1 – IntelliJ Amiya Jan 16 '18 at 09:01
added android.enableAapt2=false to gradle.properties. Pretty much the same output – kol23 Jan 16 '18 at 09:03
unfortunately this didn't work either for 4.1 it says that there is an issue with java 9.0.1 on gradle test execution while on 4.3 crashes on no item in repo – kol23 Jan 16 '18 at 12:58

Sagar · Answer 2 · 2018-03-15T11:20:05.793

5

I got the same issue and i solved it by making changes main gradle file, as per suggestion given by android studio

buildscript {
    repositories {
        jcenter()

        google()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.0.1'
    }
}

allprojects {
    repositories {
        jcenter()
        google()
    }
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

gradle-wrapper.properties :

distributionUrl=  https\://services.gradle.org/distributions/gradle-4.1-all.zip

my gradle file is like this, make like this in you project it would most probably work.

Thank you.

edited Mar 15 '18 at 11:20

answered Mar 13 '18 at 05:41

Sagar

554
5
21

1

Sorry , this made no difference. – Hristo Stoyanov Mar 13 '18 at 08:44
It is always been working for me in first try, check if you have any other issue, – Sagar Mar 14 '18 at 10:20
The idea of the topic is we are forced to use HTTP, your answer is suggesting standard https url. – Hristo Stoyanov Mar 15 '18 at 13:38

score 3 · Answer 3 · answered Mar 13 '18 at 12:27

What worked for me was to remove jcenter() and revert Gradle to an earlier version.

Unfortunately the latest stable version in bintray is 2.3.3 , but atleast I was able to build successfully.

My build.gradle now looks like this:

buildscript {
    repositories {
        maven { url "http://jcenter.bintray.com"}
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:2.3.3'

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

allprojects {
    repositories {
        maven { url "http://jcenter.bintray.com"}
    }
}

score 3 · Answer 4 · answered Mar 14 '18 at 10:20

Try this and make sure your network works well (no proxy ...) :

in gradle-wrapper.properties :

distributionUrl=  https\://services.gradle.org/distributions/gradle-4.1-all.zip

and in build.gradle:

buildscript {
    repositories {
        jcenter()
         google()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.0.1'
    }
}

allprojects {
    repositories {
        jcenter()
        google()
    }

}

score 2 · Answer 5 · answered Dec 08 '18 at 16:02

2

Add following code into your app level gradle file.

buildscript {
    repositories {
        mavenCentral()
        jcenter()
        maven { url "http://jcenter.bintray.com"}
        maven { url "http://maven.google.com"}
}

answered Dec 08 '18 at 16:02

Prashant Amage

41
2

score 1 · Answer 6 · answered Mar 15 '18 at 11:07

1

Not sure but your this error Could not resolve all files for configuration ':classpath'. When your path is not set so Follow below step:

Go to the File -> Setting -> Version Controller

Then you Change VCS to < None >

see below image :

answered Mar 15 '18 at 11:07

Ali

3,346
4
21
56

score 1 · Answer 7 · answered May 30 '18 at 11:07

I got the same issue because I used to set proxy(no proxy now) and click the OK button in proxy setting, so, check the following:

echo $proxy(mac)

/user/XXX/.gradle/gradle.properties

# systemProp.https.proxyPort=1080
# systemProp.http.proxyHost=127.0.0.1
# systemProp.https.proxyHost=127.0.0.1
# systemProp.http.proxyPort=1080

project/gradle.properties

score 1 · Answer 8 · edited Oct 08 '18 at 09:44

I had the same problem, for solving it I did the following

1- install android studio with required SDKs

2- set manual proxy in android studio: File > Settings > Appearance & Behavior > System Settings > HTTP Proxy

3- In android studio click on Gradle icon, to sync project with gradle files. Then

4- while android studio and proxy are active, in command prompt by running this command "ionic cordova build android" (I was using ionic platform), it will download all requirement gradle libraries and packages.

score 0 · Answer 9 · answered Dec 27 '18 at 16:16

0

Check that you don't filter Google IPs.

answered Dec 27 '18 at 16:16

CoolMind

26,736
15
188
224

score 0 · Answer 10 · answered Jan 16 '20 at 15:55

0

This worked for me, I needed to install google dependencies

answered Jan 16 '20 at 15:55

Johan Stiven Hernandez Osorio

329
5
8

score 0 · Answer 11 · answered Sep 11 '21 at 02:29

0

Another explanation is VPN. When my work's VPN is ON, on my Mac, I get this error. When off, I don't. Could be something particular to my VPN's configuration. So, if you have a VPN running, try disabling it turning the build.

answered Sep 11 '21 at 02:29

ncr100

58
10

score 0 · Answer 12 · answered Feb 08 '23 at 18:54

0

I had problems with the snap version of gradle in my GNU/Linux distribution.

I fixed with:

sudo snap remove  gradle
sudo apt  install gradle

answered Feb 08 '23 at 18:54

Valerio Bozz

1,176
16
32

Could not resolve com.android.tools.build.gradle:3.0.1

12 Answers12

Linked