31

See this link (as I suspected) has the POM file and no jar.

Important Notes:

  • I am using latest version of react native ... v0.57.3 and also latest version of react-native-cli ... v2.0.1 at this time.
  • I have Java 11 installed in my computer.
  • I am using latest gradle release at this time ... v4.10.2
  • I am using Mac OSX Mojave

The distribution url is:

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

Here is the error

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'AwesomePlacesApp'.
> Could not resolve all artifacts for configuration ':classpath'.
   > Could not find aapt2-proto.jar (com.android.tools.build:aapt2-proto:0.3.1).
     Searched in the following locations:
         https://jcenter.bintray.com/com/android/tools/build/aapt2-proto/0.3.1/aapt2-proto-0.3.1.jar
M.Ricciuti
  • 11,070
  • 2
  • 34
  • 54
Harry
  • 951
  • 2
  • 12
  • 18
  • Did you try any upgrades in your project? – Kosalram Ramakrishnan Oct 23 '18 at 08:40
  • Which type of upgrades @KosalramRamaKrishnan ? ... FWIW, I just edited my comment that I am using latest version of react native and react native cli ... Its a fresh project ... – Harry Oct 23 '18 at 08:47
  • 4
    Got the same error. If you follow the link you get a 404. I guess we have to wait until it is resolved by jcenter. – clash Oct 23 '18 at 08:50
  • @Harry I doubt that you might be using incompatible SDK versions. Missing jar files usually happens a lot. Just open your project in Android Studio and it will build your project freshly based on your newer versions whatever you've used in your project. Let me know if the issue persists. – Kosalram Ramakrishnan Oct 23 '18 at 08:50
  • Hey @KosalramRamaKrishnan android studio is already opened and seems like its a fresh build also ... see this image screenshot https://i.imgur.com/YY4UMzh.png ... Am I missing something sir? – Harry Oct 23 '18 at 08:54
  • Like this @jstrater (see image screenshot) ?? https://i.imgur.com/0W1XcZa.png ... After `jcenter()` function execution sir? – Harry Oct 23 '18 at 09:00
  • 2
    Maybe this will help: https://stackoverflow.com/a/52944600/4255978 – HedeH Oct 23 '18 at 09:07
  • @M.Ricciuti It's actually a duplicate. Even I shared the same link. Thanks, Harry I learned a new thing. – Kosalram Ramakrishnan Oct 23 '18 at 09:10
  • Thanks all of you guys ... I just successfully build it ... Thanks a lot ... Even I learned a new thing today ;) – Harry Oct 23 '18 at 09:21
  • Food for Thought @KosalramRamaKrishnan ... Though it works, but would like to confirm, Is this the correct code that I have changed https://i.imgur.com/t795JWr.png or am I missing something – Harry Oct 23 '18 at 09:31
  • duplicate with: https://stackoverflow.com/a/52979557/8034839 – shizhen Oct 25 '18 at 03:43

7 Answers7

49

It seems like AAPT2(Android Asset Packaging Tool 2) is available in Google's maven repository.

You need to include google() under repositories in build.gradle file as shown:

buildscript {
  repositories {
      google() // here
      jcenter()
  }
  dependencies {
      classpath 'com.android.tools.build:gradle:3.2.0-alpha12'
  }
} 
allprojects {
  repositories {
      google() // and here
      jcenter()
}

Take a look at this link for more in detail.

Note: Order also matters, if jcenter() is above google() it fails.

Kosalram Ramakrishnan
  • 818
  • 6
  • 14
15

This seems to be a jCenter issue. Until the issue is fixed you can temporarily change Android Gradle Plugin version to 3.1.0 within root build.gradle file:


    dependencies {
        classpath 'com.android.tools.build:gradle:3.1.0'
        // other imports here...
    }
azizbekian
  • 60,783
  • 13
  • 169
  • 249
3

I changed the order of this file: android/build.gradle

For me is working with this order:

buildscript {
    ext {
        buildToolsVersion = "27.0.3"
        minSdkVersion = 16
        compileSdkVersion = 27
        targetSdkVersion = 26
        supportLibVersion = "27.1.1"
    }
    repositories {
        google()        
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.2.1'
    }
}

allprojects {
    repositories {
        mavenLocal()
        google()
        jcenter()
        maven {
          url "$rootDir/../node_modules/react-native/android"
        }        
    }
}

task wrapper(type: Wrapper) {
    gradleVersion = '4.4'
    distributionUrl = distributionUrl.replace("bin", "all")
}
Fernando Poli
  • 41
  • 1
  • 5
2

This question's answer In build.gradle change position of google() and place it first: This is how it was before, if you don't have google() add it as the first one in the buildscript:

buildscript {
       repositories {
                  jcenter()
                  google()
}

change to,

buildscript {
       repositories {
               google()
               jcenter()
}
ozanurkan
  • 399
  • 4
  • 13
1

Project -> Open Module Setting -> "Project Structure - Project"

Check your Android Plugin Repository and Default Library Repository.

Note: google(), jcenter - its default value in my project.

enter image description here

Anonimys
  • 596
  • 1
  • 5
  • 14
0

You have to add google() to repositories in build.gradle file and put it at first position:

...
repositories {
    google()        
    jcenter()
}
...

In my case the problem was the repository order.

anthorlop
  • 1,771
  • 1
  • 11
  • 11
0

For me problem fixed just after gradle update, note that I had problem even with adding google() to repository

Vahid
  • 1,588
  • 4
  • 22
  • 34