Android studio 3.0 引起的 outputFile sync failed:not vaild

Posted 酸_葡_萄

tags:

篇首语:本文由小常识网(cha138.com)小编为大家整理,主要介绍了Android studio 3.0 引起的 outputFile sync failed:not vaild相关的知识,希望对你有一定的参考价值。

我们大多使用 android studio 改变生成安装包命名会用以下方式:

applicationVariants.all { variant ->

    variant.outputs.each { out ->

        def oFile =out.outputFile  // outputFile causes failure

        //...
    }
}

  但是更新到as3.0以后,会同步失败。stackoverflow上有人(http://stackoverflow.com/questions/44044031/grade-plugin-3-alpha1-outputfile-causes-error)说:

This build error occurs because variant-specific tasks are no longer created during the configuration stage.
This results in the plugin not knowing all of its outputs up front, but it also means faster configuration times.
As an alternative, we will introduce new APIs to provide similar functionality.

 

查询官网介绍:https://developer.android.com/studio/preview/features/new-android-plugin-migration.html#variant_api

API change in variant output 

  

发现解决方案:

// If you use each() to iterate through the variant objects,
// you need to start using all(). That‘s because each() iterates
// through only the objects that already exist during configuration time—
// but those object don‘t exist at configuration time with the new model.
// However, all() adapts to the new model by picking up object as they are
// added during execution.
android.applicationVariants.all { variant ->
    variant.outputs.all {
        outputFileName = "${variant.name}-${variant.versionName}.apk"
    }
}

  

以上是关于Android studio 3.0 引起的 outputFile sync failed:not vaild的主要内容,如果未能解决你的问题,请参考以下文章

Android - Android Studio 3.0去掉方法参数提示

Android Studio 3.0 安装注意点

Android - Android Studio 3.0去掉方法参数提示

Gradle plugin 3.0 & Android Studio 3.0

Android Studio 3.0 | Kotlin 测试

Android Studio 3.0找不到Android Device Monitor