【问题标题】:KotlinJvmAndroidCompilation error due to upgrade Gradle from gradle 5.6.4 to gradle 5.6.1由于将 Gradle 从 gradle 5.6.4 升级到 gradle 5.6.1 导致 KotlinJvmAndroid 编译错误
【发布时间】:2020-03-04 09:49:10
【问题描述】:

每当我将 Gradle 从 5.4.1 更新到 5.6.1 时,我都会遇到此问题,并生成以下问题。 :

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':app'.
> Failed to notify project evaluation listener.
   > No value has been specified for this provider.
   > KotlinJvmAndroidCompilation with name 'productionDebug' not found.

* Try:
Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Exception is:
org.gradle.api.ProjectConfigurationException: A problem occurred configuring project ':app'.
    at org.gradle.configuration.project.LifecycleProjectEvaluator.wrapException(LifecycleProjectEvaluator.java:80)
    at org.gradle.configuration.project.LifecycleProjectEvaluator.addConfigurationFailure(LifecycleProjectEvaluator.java:73)
    at org.gradle.configuration.project.LifecycleProjectEvaluator.access$600(LifecycleProjectEvaluator.java:53)
    at org.gradle.configuration.project.LifecycleProjectEvaluator$NotifyAfterEvaluate.run(LifecycleProjectEvaluator.java:199)
    at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:402)
    at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:394)
    at org.gradle.internal.operations.DefaultBuildOperationExecutor$1.execute(DefaultBuildOperationExecutor.java:165)
    at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:250)
    at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:158)
    at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:92)
    at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
    at org.gradle.configuration.project.LifecycleProjectEvaluator$EvaluateProject$1.run(LifecycleProjectEvaluator.java:112)
    at org.gradle.internal.Factories$1.create(Factories.java:26)

    at org.gradle.internal.event.AbstractBroadcastDispatch.dispatch(AbstractBroadcastDispatch.java:58)
    ... 125 more


* Get more help at https://help.gradle.org

CONFIGURE FAILED in 2s

使用 - kotlin 版本 v1.3.70 - Gradle v5.6.4 - Android Studio v3.6.1

请帮忙。 提前致谢

【问题讨论】:

标签: android-studio android-gradle-plugin


【解决方案1】:

我遇到了同样的问题,结果发现问题的原因是结构 gradle 插件(crashlytics)而不是 gradle 本身。

基本上,使用io.fabric.tools:gradle:1.31.2 结构插件在build.gradle 文件中设置ext.enableCrashlytics = true 时会出现问题。

解决方法

您必须避免将ext.enableCrashlytics 显式设置为truefalse 可以)。

例如可以替换如下代码

def enableCrashlytics = // comes from somewhere
ext.enableCrashlytics = enableCrashlytics

通过

def enableCrashlytics = // comes from somewhere
if (!enableCrashlytics) {
    ext.enableCrashlytics = false
}

由于默认情况下启用了 crashlytics,因此行为保持不变。

作为替代方案,您可以恢复使用1.31.0,它工作正常,但我不建议这样做,因为最新版本包含几个关键的bug fixes

此外,您可以考虑迁移到 Firebase Crashlytics(目前处于测试阶段),因为 Google 很快会为 Fabric 提供 dropping support,而且此问题可能无法解决。

最初回答here

【讨论】:

    猜你喜欢
    • 1970-01-01
    • 1970-01-01
    • 2021-11-25
    • 2013-07-12
    • 2021-03-07
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    相关资源
    最近更新 更多