无法确定任务“:app:lintVitalRelease"的依赖关系.无法生成签名的 APK [英] Could not determine the dependencies of task ':app:lintVitalRelease'. Can't generate signed APK

查看:660
本文介绍了无法确定任务“:app:lintVitalRelease"的依赖关系.无法生成签名的 APK的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

最近我在当前的 java 项目中添加了一些 kotlin 活动和一个库项目.我可以毫无问题地运行项目.clean - build - rebuild - run 一切正常.

Recently I added some kotlin activities and a library project to current java project. I can run project without any problem. clean - build - rebuild - run all are ok.

生成签名APK时出现问题.我收到以下错误:

the problem appears when generating signed APK. I get below error:

Could not determine the dependencies of task ':app:lintVitalRelease'.
> Could not resolve all artifacts for configuration ':app:buildCompileClasspath'.
   > Could not resolve project :my_library.
     Required by:
         project :app
      > No matching variant of project :my_library was found. The consumer was configured to find an API of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'build', attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' but:
          - Variant 'debugApiElements' capability My_project:my_library:unspecified declares an API of a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm':
              - Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'build'
          - Variant 'debugRuntimeElements' capability My_project:my_library:unspecified declares a runtime of a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm':
              - Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'build'
          - Variant 'debugTestApiElements' capability My_project:my_library:unspecified declares an API of a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm':
              - Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debugTest' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'build'
          - Variant 'debugTestRuntimeElements' capability My_project:my_library:unspecified declares a runtime of a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm':
              - Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debugTest' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'build'
          - Variant 'releaseApiElements' capability My_project:my_library:unspecified declares an API of a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm':
              - Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'build'
          - Variant 'releaseRuntimeElements' capability My_project:my_library:unspecified declares a runtime of a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm':
              - Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'build'


gradle file in project level :

    buildscript {
    ext.kotlin_version = '1.5.0'
    ext {
        projectMinSdkVersion = 16      // 15 android 4.0.3 for release
        projectTargetSdkVersion = 30   //23 requires permission requests , 22 for release
    }
    repositories {
        google()
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:4.1.3'
//        classpath 'com.android.tools.build:gradle:4.2.2'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
//        classpath 'com.google.gms:google-services:4.3.4'//
        classpath 'com.google.gms:google-services:4.3.10'//
        classpath 'com.google.firebase:firebase-crashlytics-gradle:2.7.1' //
    }

}
//plugins {
//    id 'nebula.lint' version '9.3.4'
//}
allprojects {
    repositories {
        google()
        jcenter()
        maven { url "https://jitpack.io" }
//        maven {
  //          url "https://maven.google.com" // Google's Maven repository
    //    }
        tasks.withType(JavaCompile) {
            options.compilerArgs << "-Xlint:deprecation"
        }

    }
}

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

库级别的插件:

    apply plugin: 'com.android.library'
apply plugin: 'kotlin-android'
apply plugin: 'kotlin-android-extensions'

应用级别的插件:

    apply plugin: 'com.android.application'
apply plugin: 'kotlin-android'
apply plugin: 'kotlin-android-extensions'

有什么想法吗?

推荐答案

我找到了解决方案,感谢 @Fabio.问题出在 buildTypes 结构中.所以,在应用级别我有 releasebuild,但在库级别我有 releasedebug.

I found the solution, thanks to @Fabio. The problem was in buildTypes structure. so, in app level I have release and build, but in library level I have release and debug.

我将库级别的 buildTypes 更改为与应用级别相同:

I changed buildTypes in library level like this to be same like in app level:

buildTypes {
    release {
        // minifyEnabled false
        // proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    }

    build {
        //   minifyEnabled false
        //   proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    }

因此,如果需要,我建议从应用级别和每个构建中的注释行复制它.

so, I would recommend to copy it from app level and comment lines inside each build if required.

这篇关于无法确定任务“:app:lintVitalRelease"的依赖关系.无法生成签名的 APK的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆