Gradle错误:找不到com.android.tools.build:gradle:2.2.+的任何匹配项

时间:2018-12-10 19:26:39

标签: android android-studio android-gradle jcenter

这是一个React Native项目。在另一台机器上可以正常工作,但是一旦移到我的机器上,它将失败。

我找到的大多数解决方案建议将jcenter()添加到项目级别gradle.build的存储库中。就我而言,它已经被添加了。

Gradle同步失败,并显示以下错误:

Could not find any matches for com.android.tools.build:gradle:2.2.+ as no versions of com.android.tools.build:gradle are available. Searched in the following locations: https://jcenter.bintray.com/com/android/tools/build/gradle/maven-metadata.xml https://jcenter.bintray.com/com/android/tools/build/gradle/ Required by: project :react-native-image-picker

Android build.gradle文件:

// Top-level build file where you can add configuration options common to all sub-projects/modules.

buildscript {
    repositories {
        google()
        mavenLocal()
        mavenCentral()
        jcenter()

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

allprojects {
    repositories {
        google()
        mavenCentral()
        mavenLocal()
        jcenter()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url "$rootDir/../node_modules/react-native/android"
        }

       maven { url 'https://jitpack.io' }
    }
}

ext {
    buildToolsVersion = "27.0.3"
    minSdkVersion = 19
    compileSdkVersion = 26
    targetSdkVersion = 26
    supportLibVersion = "26.1.0"

    googlePlayServicesVersion = "11.8.0"
    androidMapsUtilsVersion = "0.5+"
}
subprojects { subproject ->
    afterEvaluate {
        if ((subproject.plugins.hasPlugin('android') || subproject.plugins.hasPlugin('android-library'))) {
            android {
                variantFilter { variant ->
                    def names = variant.flavors*.name
                    if (names.contains("reactNative51") || names.contains("reactNative55")) {
                        setIgnore(true)
                    }
                }
            }
        }
    }
}
}

应用程序build.gradle:

apply plugin: "com.android.application"

import com.android.build.OutputFile

/**
 * The react.gradle file registers a task for each build variant (e.g. bundleDebugJsAndAssets
 * and bundleReleaseJsAndAssets).
 * These basically call `react-native bundle` with the correct arguments during the Android build
 * cycle. By default, bundleDebugJsAndAssets is skipped, as in debug/dev mode we prefer to load the
 * bundle directly from the development server. Below you can see all the possible configurations
 * and their defaults. If you decide to add a configuration block, make sure to add it before the
 * `apply from: "../../node_modules/react-native/react.gradle"` line.
 *
 * project.ext.react = [
 *   // the name of the generated asset file containing your JS bundle
 *   bundleAssetName: "index.android.bundle",
 *
 *   // the entry file for bundle generation
 *   entryFile: "index.android.js",
 *
 *   // whether to bundle JS and assets in debug mode
 *   bundleInDebug: false,
 *
 *   // whether to bundle JS and assets in release mode
 *   bundleInRelease: true,
 *
 *   // whether to bundle JS and assets in another build variant (if configured).
 *   // See http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Build-Variants
 *   // The configuration property can be in the following formats
 *   //         'bundleIn${productFlavor}${buildType}'
 *   //         'bundleIn${buildType}'
 *   // bundleInFreeDebug: true,
 *   // bundleInPaidRelease: true,
 *   // bundleInBeta: true,
 *
 *   // whether to disable dev mode in custom build variants (by default only disabled in release)
 *   // for example: to disable dev mode in the staging build type (if configured)
 *   devDisabledInStaging: true,
 *   // The configuration property can be in the following formats
 *   //         'devDisabledIn${productFlavor}${buildType}'
 *   //         'devDisabledIn${buildType}'
 *
 *   // the root of your project, i.e. where "package.json" lives
 *   root: "../../",
 *
 *   // where to put the JS bundle asset in debug mode
 *   jsBundleDirDebug: "$buildDir/intermediates/assets/debug",
 *
 *   // where to put the JS bundle asset in release mode
 *   jsBundleDirRelease: "$buildDir/intermediates/assets/release",
 *
 *   // where to put drawable resources / React Native assets, e.g. the ones you use via
 *   // require('./image.png')), in debug mode
 *   resourcesDirDebug: "$buildDir/intermediates/res/merged/debug",
 *
 *   // where to put drawable resources / React Native assets, e.g. the ones you use via
 *   // require('./image.png')), in release mode
 *   resourcesDirRelease: "$buildDir/intermediates/res/merged/release",
 *
 *   // by default the gradle tasks are skipped if none of the JS files or assets change; this means
 *   // that we don't look at files in android/ or ios/ to determine whether the tasks are up to
 *   // date; if you have any other folders that you want to ignore for performance reasons (gradle
 *   // indexes the entire tree), add them here. Alternatively, if you have JS files in android/
 *   // for example, you might want to remove it from here.
 *   inputExcludes: ["android/**", "ios/**"],
 *
 *   // override which node gets called and with what additional arguments
 *   nodeExecutableAndArgs: ["node"],
 *
 *   // supply additional arguments to the packager
 *   extraPackagerArgs: []
 * ]
 */

project.ext.react = [
    entryFile: "index.js"
]

apply from: "../../node_modules/react-native/react.gradle"

/**
 * Set this to true to create two separate APKs instead of one:
 *   - An APK that only works on ARM devices
 *   - An APK that only works on x86 devices
 * The advantage is the size of the APK is reduced by about 4MB.
 * Upload all the APKs to the Play Store and people will download
 * the correct one based on the CPU architecture of their device.
 */
def enableSeparateBuildPerCPUArchitecture = false

/**
 * Run Proguard to shrink the Java bytecode in release builds.
 */
def enableProguardInReleaseBuilds = false

android {
    compileSdkVersion rootProject.ext.compileSdkVersion
    buildToolsVersion rootProject.ext.buildToolsVersion

    defaultConfig {
        applicationId "com.sos"
        minSdkVersion rootProject.ext.minSdkVersion
        targetSdkVersion rootProject.ext.targetSdkVersion
        versionCode 1
        versionName "1.0"
  missingDimensionStrategy "RNN.reactNativeVersion", "reactNative57"

        ndk {
            abiFilters "armeabi-v7a", "x86"
        }
    }
    splits {
        abi {
            reset()
            enable enableSeparateBuildPerCPUArchitecture
            universalApk false  // If true, also generate a universal APK
            include "armeabi-v7a", "x86"
        }
    }
        signingConfigs {
        release {
            if (project.hasProperty('MYAPP_RELEASE_STORE_FILE')) {
                storeFile file(MYAPP_RELEASE_STORE_FILE)
                storePassword MYAPP_RELEASE_STORE_PASSWORD
                keyAlias MYAPP_RELEASE_KEY_ALIAS
                keyPassword MYAPP_RELEASE_KEY_PASSWORD
            }
        }
    }
    buildTypes {
        release {
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
            signingConfig signingConfigs.release

        }
    }
    // applicationVariants are e.g. debug, release
    applicationVariants.all { variant ->
        variant.outputs.each { output ->
            // For each separate APK per architecture, set a unique version code as described here:
            // http://tools.android.com/tech-docs/new-build-system/user-guide/apk-splits
            def versionCodes = ["armeabi-v7a":1, "x86":2]
            def abi = output.getFilter(OutputFile.ABI)
            if (abi != null) {  // null for the universal-debug, universal-release variants
                output.versionCodeOverride =
                        versionCodes.get(abi) * 1048576 + defaultConfig.versionCode
            }
        }
    }
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }
}
configurations.all {
    resolutionStrategy.eachDependency { DependencyResolveDetails details ->
        def requested = details.requested
        if (requested.group == 'com.android.support' && requested.name != 'multidex') {
            details.useVersion "${rootProject.ext.supportLibVersion}"
        }
    }
}
dependencies {
    implementation project(':react-native-fetch-blob')
    implementation project(':react-native-linear-gradient')
    implementation project(':react-native-maps')
    implementation project(':react-native-image-picker')
    implementation project(':react-native-vector-icons')
    implementation fileTree(dir: "libs", include: ["*.jar"])
    implementation "com.android.support:appcompat-v7:${rootProject.ext.supportLibVersion}"
    implementation "com.facebook.react:react-native:+"  // From node_modules
    implementation project(':react-native-navigation')
    implementation 'com.android.support:design:25.4.0'
    implementation "com.android.support:appcompat-v7:${rootProject.ext.supportLibVersion}"
    implementation project(':react-native-maps')
}


// Run this once to be able to run the application with BUCK
// puts all compile dependencies into folder libs for BUCK to use
task copyDownloadableDepsToLibs(type: Copy) {
    from configurations.compile
    into 'libs'
}

顺便说一句,在应用程序build.gralde文件中,android中的import com.android.build.OutputFile引发错误:无法解决

编辑:

现在,构建过程的这一部分已成功通过,但是我开始遇到此错误: Unable to find a matching configuration of project :react-native-fetch-blob: None of the consumable configurations have attributes.

enter image description here

7 个答案:

答案 0 :(得分:26)

如果您不想等到该库发布固定版本,可以通过以下方法进行修复:

只需将其添加到根目录(而不是app / gradle)子项目下的build.gradle中

subprojects {
    if (project.name.contains('react-native-image-picker') || 
        project.name.contains('react-native-vector-icons')) {
        buildscript {
            repositories {
                jcenter()
                maven { url "https://dl.bintray.com/android/android-tools/"  }
            }
        }
    }
}

贷方转到https://github.com/akolpakov

答案 1 :(得分:10)

这是一个新问题,新版本的react-native-image-picker已解决 转到您的根文件夹,然后重新安装react-native-image-picker:

npm install --save react-native-image-picker

然后转到您的根文件夹,并确保您的react-native-image-picker版本为“ ^ 0.27.2”

答案 2 :(得分:4)

react-native-vector-icons软件包也遇到相同的问题。

这是由这两个存储库损坏引起的吗?

https://jcenter.bintray.com/com/android/tools/build/gradle/maven-metadata.xml
https://jcenter.bintray.com/com/android/tools/build/gradle/

他们都回答“未找到请求的路径。”

修改

基于日志信息:

project :react-native-vector-icons 
com.intellij.openapi.externalSystem.model.ExternalSystemException: 
Could not find any matches for com.android.tools.build:gradle:2.3.+ as 
no versions of com.android.tools.build:gradle are available.

搜索'2.3。+'并将其替换为明确的版本号(例如2.3.0) 该问题将得到解决。

我已经阅读了Android上关于避免在版本代码中使用+的建议,该建议现在可以强制执行。

答案 3 :(得分:4)

在提出此问题的当天-2018年12月10日-持续了一天的问题,因为JCenter收到了Google要求从其存储库中删除多个二进制文件的请求:

  

Google要求我们停止提供其二进制文件。请为他们使用官方的Google存储库。   https://twitter.com/bintray/status/1072275597315923971

如果您需要立即解决方法,最好的做法是直接在其Maven URL中添加所需的任何依赖项。例如。: repositories { (...) maven { url 'https://dl.bintray.com/android/android-tools' } } https://issuetracker.google.com/issues/120759347#comment3

上面的线程是跟踪问题解决的好地方,因为在我撰写本文时仍在继续。

答案 4 :(得分:4)

似乎某些存储库被错误地删除了,据Google代表称,这是他们目前正在恢复的工作:

https://issuetracker.google.com/issues/120759347#comment30

  

大家好,

     

我们现在知道发生了什么,并且正在努力将其回滚到   明智的方式。这是问题的基本概述:

     
      
  1. jCenter上有一些伪造/格式错误的com.google。*和com.android。*工件
  2.   
  3. 这些工件大多数都已正确托管在maven.google.com(aka google())
  4.   
  5. 如果您的构建系统在找到jCenter版本之前找到了jCenter版本,那么您的构建将被破坏
  6.   
  7. Google注意到了这一点,并要求jFrog删除com.google。*和com.android。*下的所有内容,因为我们认为是   也在Google Maven上全部
  8.   
  9. 我们错了:-(
  10.   
  11. 从jCenter删除的某些工件会导致构建错误
  12.   
     

我们正在做一些事情:

     
      
  • 一些已删除的库正被推送到Google Maven。   这包括com.google.gms:google-services插件,firebase   性能插件和Exoplayer。尝试将google()添加到您的   buildscript和应用程序存储库块以查看是否有帮助。我们   希望这可以帮助很多人,但不是所有人。 *我们正在工作   列出未正确删除的库。一些   上面第4步中删除的操作是有充分理由的,因此我们   也不想还原它们。
  •   
     

正如我之前所说,我们讨厌破坏您的作品,我们对此表示赞赏   您在我们修复它时的耐心!

     
      
  • 山姆
  •   

同时,他们还建议以下解决方法:

https://issuetracker.google.com/issues/120759347#comment36

  

状态

     
      
  • Google服务库(com.google.gms:google-services)库已恢复,请参阅更新#31。
  •   
  • 请求已提交给jCenter,以重新发布在bintray.com/google上托管的所有存储库。 JFrog的jCenter管理员   正在努力使他们恢复在线状态,目前我们已经可以   就是等待。我们希望他们尽快上线。一些图书馆是   已经回来了。
  •   
  • 在jcenter.bintray.com和maven.google.com上双宿主的某些Android / Firebase库缺少旧版本   (以前托管在jCenter上)。我们仍在努力获取这些   通过jcenter.bintray.com或maven.google.com返回在线状态,   适当-我们在这里要谨慎工作,以避免重新创建   引发问题的最初冲突。工作正在进行中。较新的   这些库的版本不受影响,因为它们在   maven.google.com。
  •   
     

WORKAROUNDS

     
      
  1. 对于Google Services库,无需任何解决方法。该库已还原。 / google中的其他库位于   恢复的进度。
  2.   
  3. 对于从bintray.com/android或bintray.com/firebase提供的无法解决的项目,请考虑升级到   已托管在maven.google.com上的较新版本。 (见下文   如果这不可行。)
  4.   
  5. 对于bintray.com/google中的项目,或者如果您无法升级到Android或Firebase库的较新版本...   需要暂时向您添加类似于以下内容的代码块   build.gradle:

         

    存储库{      专家{          网址“ https://google.bintray.com/ $(资源)”      }

         

    将$(REPOSITORY)替换为项目名称来自   https://bintray.com/google

         

    对于bintray.com/firebase,请使用   “ https://firebase.bintray.com/ $(库存)”。对于bintray.com/android,   使用“ https://dl.bintray.com/android/ $(库存)”。

         

    同样,此解决方法只是暂时的,直到我们能够获得所有   版本在jCenter中重新列出或镜像到   maven.google.com。

  6.   
     

调查

     

从jCenter提交到除名项目的请求似乎范围太广,并且是由   Google的另一个没有完全授权的团队   更改。在此之前未咨询过Google的存储库管理员   该请求已由jCenter执行。我们将在   在未来的日子里,现在我们的首要任务是恢复访问   受影响的库的所有版本。

     

此外,似乎可能存在配置错误   Google的存储库阻止了maven.google.com的镜像   进入jCenter,这又是最初删除的原因   请求。纠正这种错误配置可能避免了   删除任何东西。内部还有其他后续行动。

答案 5 :(得分:2)

尝试使用对我有用的gradle的确切版本

classpath 'com.android.tools.build:gradle:2.2.3'

答案 6 :(得分:1)

对于使用react-native-vector-icons软件包遇到此错误的人:

  1. 升级package.json中的“ react-native-vector-icons”:“ ^ 6.0.2”

来源:https://github.com/oblador/react-native-vector-icons/issues/605#issuecomment-446081342