Home > other >  "Could not find com.android.tools.build:gradle:7.2.0." with Chipmunk
"Could not find com.android.tools.build:gradle:7.2.0." with Chipmunk

Time:05-10

I have just updated Android Studio to Chipmunk and gradle file sync no longer works. The sync has the following errors:

Could not find com.android.tools.build:gradle:7.2.0.
Searched in the following locations:
  - https://dl.google.com/dl/android/maven2/com/android/tools/build/gradle/7.2.0/gradle-7.2.0.pom
  - https://repo.maven.apache.org/maven2/com/android/tools/build/gradle/7.2.0/gradle-7.2.0.pom
Required by:
    project :
Add google Maven repository and sync project
Open File

I clicked "Add google Maven repository and sync project" but nothing happened. I have the following in build.gradle:

buildscript {
    ext.kotlin_version = '1.3.72'
    repositories {
        google()
        mavenCentral()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:7.2.0'


        classpath("com.google.android.gms:oss-licenses-plugin:0.10.5")

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

Could anyone offer a tip on how to fix this?

Android Studio Chipmunk | 2021.2.1
Build #AI-212.5712.43.2112.8512546, built on April 28, 2022
Runtime version: 11.0.12 7-b1504.28-7817840 amd64
VM: OpenJDK 64-Bit Server VM by Oracle Corporation
Windows 10 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 4096M
Cores: 16
Registry: external.system.auto.import.disabled=true, debugger.watches.in.variables=false
Non-Bundled Plugins: org.intellij.plugins.markdown (212.5457.16), com.thoughtworks.gauge (212.4746.52), org.jetbrains.kotlin (212-1.6.21-release-334-AS5457.46), com.android.aas (3.5.1), com.intellij.marketplace (212.5712.51), com.google.mad-scorecard (1.2)

CodePudding user response:

AGP 7.2.0 was released just some minutes ago and was not available earlier today yet. Try again.

CodePudding user response:

As there is no such release listed on that site, this might be a bug. Use version 7.1.3 instead.

  • Related