开源项目运行时报错A problem was found with the configuration of task ‘:app:checkDebugManifest‘

这篇具有很好参考价值的文章主要介绍了开源项目运行时报错A problem was found with the configuration of task ‘:app:checkDebugManifest‘。希望对大家有所帮助。如果存在错误或未考虑完全的地方,请大家不吝赐教,您也可以点击"举报违法"按钮提交疑问。

下载开源项目后,对gradle-wrapper.properties中的gradle版本进行了升级,造成了如下问题:

1: Task failed with an exception.

-----------

* What went wrong:

A problem was found with the configuration of task ':app:checkDebugManifest' (type 'CheckManifest').

  - Type 'com.android.build.gradle.internal.tasks.CheckManifest' property 'manifest' has @Input annotation used on property of type 'File'.

   

    Reason: A property of type 'File' annotated with @Input cannot determine how to interpret the file.

   

    Possible solutions:

      1. Annotate with @InputFile for regular files.

      2. Annotate with @InputDirectory for directories.

      3. If you want to track the path, return File.absolutePath as a String and keep @Input.

   

    Please refer to https://docs.gradle.org/7.0.2/userguide/validation_problems.html#incorrect_use_of_input_annotation for more details about this problem.

* Try:

Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

==============================================================================

2: Task failed with an exception.

-----------

* What went wrong:

A problem was found with the configuration of task ':lib_multiple_view:packageDebugResources' (type 'MergeResources').

  - Type 'com.android.build.gradle.tasks.MergeResources' property 'resourcesComputer' is missing an input or output annotation.

   

    Reason: A property without annotation isn't considered during up-to-date checking.

   

    Possible solutions:

      1. Add an input or output annotation.

      2. Mark it as @Internal.

   

    Please refer to https://docs.gradle.org/7.0.2/userguide/validation_problems.html#missing_annotation for more details about this problem.

* Try:

Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

==============================================================================

3: Task failed with an exception.

-----------

* What went wrong:

A problem was found with the configuration of task ':app:createDebugCompatibleScreenManifests' (type 'CompatibleScreensManifest').

  - Type 'com.android.build.gradle.tasks.CompatibleScreensManifest' property 'outputScope' is missing an input or output annotation.

   

    Reason: A property without annotation isn't considered during up-to-date checking.

   

    Possible solutions:

      1. Add an input or output annotation.

      2. Mark it as @Internal.

   

    Please refer to https://docs.gradle.org/7.0.2/userguide/validation_problems.html#missing_annotation for more details about this problem.

* Try:

Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

==============================================================================

4: Task failed with an exception.

-----------

* What went wrong:

A problem was found with the configuration of task ':lib_multiple_view:checkDebugManifest' (type 'CheckManifest').

  - Type 'com.android.build.gradle.internal.tasks.CheckManifest' property 'manifest' has @Input annotation used on property of type 'File'.

   

    Reason: A property of type 'File' annotated with @Input cannot determine how to interpret the file.

   

    Possible solutions:

      1. Annotate with @InputFile for regular files.

      2. Annotate with @InputDirectory for directories.

      3. If you want to track the path, return File.absolutePath as a String and keep @Input.

   

    Please refer to https://docs.gradle.org/7.0.2/userguide/validation_problems.html#incorrect_use_of_input_annotation for more details about this problem.

* Try:

Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

==============================================================================

5: Task failed with an exception.

-----------

* What went wrong:

A problem was found with the configuration of task ':app:tinkerProcessDebugManifest' (type 'TinkerManifestTask').

  - Type 'com.tencent.tinker.build.gradle.task.TinkerManifestTask' property 'manifestPath' is missing an input or output annotation.

   

    Reason: A property without annotation isn't considered during up-to-date checking.

   

    Possible solutions:

      1. Add an input or output annotation.

      2. Mark it as @Internal.

   

    Please refer to https://docs.gradle.org/7.0.2/userguide/validation_problems.html#missing_annotation for more details about this problem.

* Try:

Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

==============================================================================

6: Task failed with an exception.

-----------

* What went wrong:

Some problems were found with the configuration of task ':app:tinkerSupportProcessDebugManifest' (type 'TinkerSupportManifestTask').

  - Type 'com.tencent.bugly.build.gradle.tasks.TinkerSupportManifestTask' property 'dateString' is missing an input or output annotation.

   

    Reason: A property without annotation isn't considered during up-to-date checking.

   

    Possible solutions:

      1. Add an input or output annotation.

      2. Mark it as @Internal.

   

    Please refer to https://docs.gradle.org/7.0.2/userguide/validation_problems.html#missing_annotation for more details about this problem.

  - Type 'com.tencent.bugly.build.gradle.tasks.TinkerSupportManifestTask' property 'hasFlavors' has redundant getters: 'getHasFlavors()' and 'isHasFlavors()'.

   

    Reason: Boolean property 'hasFlavors' has both an `is` and a `get` getter.

   

    Possible solutions:

      1. Remove one of the getters.

      2. Annotate one of the getters with @Internal.

   

    Please refer to https://docs.gradle.org/7.0.2/userguide/validation_problems.html#redundant_getters for more details about this problem.

  - Type 'com.tencent.bugly.build.gradle.tasks.TinkerSupportManifestTask' property 'hasFlavors' is missing an input or output annotation.

   

    Reason: A property without annotation isn't considered during up-to-date checking.

   

    Possible solutions:

      1. Add an input or output annotation.

      2. Mark it as @Internal.

   

    Please refer to https://docs.gradle.org/7.0.2/userguide/validation_problems.html#missing_annotation for more details about this problem.

  - Type 'com.tencent.bugly.build.gradle.tasks.TinkerSupportManifestTask' property 'manifestPath' is missing an input or output annotation.

   

    Reason: A property without annotation isn't considered during up-to-date checking.

   

    Possible solutions:

      1. Add an input or output annotation.

      2. Mark it as @Internal.

   

    Please refer to https://docs.gradle.org/7.0.2/userguide/validation_problems.html#missing_annotation for more details about this problem.

  - Type 'com.tencent.bugly.build.gradle.tasks.TinkerSupportManifestTask' property 'now' is missing an input or output annotation.

   

    Reason: A property without annotation isn't considered during up-to-date checking.

   

    Possible solutions:

      1. Add an input or output annotation.

      2. Mark it as @Internal.

   

    Please refer to https://docs.gradle.org/7.0.2/userguide/validation_problems.html#missing_annotation for more details about this problem.

* Try:

Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

==============================================================================

7: Task failed with an exception.

-----------

* What went wrong:

Execution failed for task ':lib_multiple_view:compileDebugJavaWithJavac'.

> Failed to query the value of task ':lib_multiple_view:compileDebugJavaWithJavac' property 'options.generatedSourceOutputDirectory'.

   > Querying the mapped value of map(java.io.File task ':lib_multiple_view:compileDebugJavaWithJavac' property 'annotationProcessorSourcesDirectory' org.gradle.api.internal.file.DefaultFilePropertyFactory$ToFileTransformer@28fd5bb0) before task ':lib_multiple_view:compileDebugJavaWithJavac' has completed is not supported

* Try:

Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

==============================================================================

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

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

Use '--warning-mode all' to show the individual deprecation warnings.

See https://docs.gradle.org/7.0.2/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 6s

9 actionable tasks: 6 executed, 3 up-to-date

解决方法

将gradle-wrapper.properties中的gradle版本降级

distributionUrl=https\://services.gradle.org/distributions/gradle-7.0.2-bin.zip

修改为 

distributionUrl=https\://services.gradle.org/distributions/gradle-6.1.1-all.zip文章来源地址https://www.toymoban.com/news/detail-402941.html

到了这里,关于开源项目运行时报错A problem was found with the configuration of task ‘:app:checkDebugManifest‘的文章就介绍完了。如果您还想了解更多内容,请在右上角搜索TOY模板网以前的文章或继续浏览下面的相关文章,希望大家以后多多支持TOY模板网!

本文来自互联网用户投稿,该文观点仅代表作者本人,不代表本站立场。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如若转载,请注明出处: 如若内容造成侵权/违法违规/事实不符,请点击违法举报进行投诉反馈,一经查实,立即删除!

领支付宝红包 赞助服务器费用

相关文章

觉得文章有用就打赏一下文章作者

支付宝扫一扫打赏

博客赞助

微信扫一扫打赏

请作者喝杯咖啡吧~博客赞助

支付宝扫一扫领取红包,优惠每天领

二维码1

领取红包

二维码2

领红包