Android studio 升级3.0后出现的bug解决办法！

Android studio 升级3.0后出现的bug解决办法！

-----------------

博主github： 

https://github.com/kkman2008

-------------------

 

android studio 提示有3.0更新，强迫症就直接升级了，结果就尴尬了！
出现问题然后就去找解决办法：看到这篇文章
http://blog.csdn.net/qqcrazyboy/article/details/77900183

内容如下：
1.现象描述
原来项目在Android studio 2.3一切正常，升级3.0之后报如下错误：

Error:Cannot choose between the following configurations of project :android_sdk: - debugApiElements - debugRuntimeElements - releaseApiElements - releaseRuntimeElementsAll of them match the consumer attributes: - Configuration 'debugApiElements': - Found com.android.build.api.attributes.BuildTypeAttr 'debug' but wasn't required. - Found com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' but wasn't required. - Found com.android.build.gradle.internal.dependency.VariantAttr 'debug' but wasn't required. - Found org.gradle.api.attributes.Usage 'java-api' but wasn't required. - Configuration 'debugRuntimeElements': - Found com.android.build.api.attributes.BuildTypeAttr 'debug' but wasn't required. - Found com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' but wasn't required. - Found com.android.build.gradle.internal.dependency.VariantAttr 'debug' but wasn't required. - Found org.gradle.api.attributes.Usage 'java-runtime' but wasn't required. - Configuration 'releaseApiElements': - Found com.android.build.api.attributes.BuildTypeAttr 'release' but wasn't required. - Found com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' but wasn't required. - Found com.android.build.gradle.internal.dependency.VariantAttr 'release' but wasn't required. - Found org.gradle.api.attributes.Usage 'java-api' but wasn't required. - Configuration 'releaseRuntimeElements': - Found com.android.build.api.attributes.BuildTypeAttr 'release' but wasn't required. - Found com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' but wasn't required. - Found com.android.build.gradle.internal.dependency.VariantAttr 'release' but wasn't required. - Found org.gradle.api.attributes.Usage 'java-runtime' but wasn't required.

2.解决办法：
project的build.gradle
文件中删除

classpath 'com.neenbedankt.gradle.plugins:android-apt:1.8'

module的build.gradle
文件中删除

apply plugin: 'com.neenbedankt.android-apt'

module的build.gradle
文件中替换

//apt 'com.jakewharton:butterknife-compiler:8.0.1
'annotationProcessor 'com.jakewharton:butterknife-compiler:8.0.1'

然后又出现了新的问题：

Error:All flavors must now belong to a named flavor dimension. Learn more at https://d.android.com/r/tools/flavorDimensions-missing-error-message.html

然后又百度找解决办法，真的是急死我了。终于看到这篇文章：
http://blog.csdn.net/syif88/article/details/75009663

内容如下：
这个问题是Android studio升级到3.0之后，运行的时候会提示gradle要升级到3.5版本才能编译。于是我把我的gradle升级到了 gradle-4.1-milestone-1 版本，是2017年7月份最新版本了。
于是我把主程序的build.gradle中的gradle版本改成了这个，具体指定哪个版本我也不知道，于是就写了个3.0+

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

然后再次编译，又发现了毒。
提示：Error:All flavors must now belong to a named flavor dimension.Learn more at https://d.android.com/r/tools/flavorDimensions-missing-error-message.html
这个一个错误，意思是：所有的flavors都必须属于同一个风格。
=。=懵逼
去看了它提供的地址才知道：

Plugin 3.0.0 includes a new dependency mechanism that automatically matches variants when consuming a library. This means an app's debug variant automatically consumes a library's debug variant, and so on. It also works when using flavors—an app's redDebug variant will consume a library's redDebug variant. To make this work, the plugin now requires that all flavors belong to a named flavor dimension —even if you intend to use only a single dimension. Otherwise, you will get the following build error:
[cpp] view plain copy

Error:All flavors must now belong to a named flavor dimension.
The flavor 'flavor_name' is not assigned to a flavor dimension.

To resolve this error, assign each flavor to a named dimension, as shown in the sample below. Because dependency matching is now taken care of by the plugin, you should name your flavor dimensions carefully. For example, if all your app and library modules use the foo dimension, you'll have less control over which flavors are matched by the plugin.
[cpp] view plain copy

// Specifies a flavor dimension.
flavorDimensions "color"

productFlavors {
red {
// Assigns this product flavor to the 'color' flavor dimension.
// This step is optional if you are using only one dimension.
dimension "color"
...
}

blue {  
  dimension "color"  
  ...  
}  

}

大致是说，Plugin 3.0.0之后有一种自动匹配消耗库的机制，便于debug variant 自动消耗一个库，然后就是必须要所有的flavor 都属于同一个维度。
为了避免flavor 不同产生误差的问题，应该在所有的库模块都使用同一个foo尺寸。
= 。=还是懵逼。说一堆依然不是很理解。
但是我们从中已经知道解决方案了：
在主app的build.gradle里面的

defaultConfig {
targetSdkVersion：minSdkVersion ：
versionCode：***
versionName ：***

//版本名后面添加一句话，意思就是flavor dimension 它的维度就是该版本号，这样维度就是都是统一的了
flavorDimensions "versionCode"
}

就直接解决这个问题。然后app 就可以happy的运行起来了。

但是很不幸构建是成功了，但是运行时又出现了这个问题：

Error:Execution failed for task ':data:javaPreCompileDebug'.
Annotation processors must be explicitly declared now. The following dependencies on the compile classpath are found to contain annotation processor. Please add them to the annotationProcessor configuration.
- auto-value-gson-0.4.2.jar (com.ryanharter.auto.value:auto-value-gson:0.4.2)
- auto-value-1.3-rc1.jar (com.google.auto.value:auto-value:1.3-rc1)
Alternatively, set android.defaultConfig.javaCompileOptions.annotationProcessorOptions.includeCompileClasspath = true to continue with previous behavior. Note that this option is deprecated and will be removed in the future.
See https://developer.android.com/r/tools/annotation-processor-error-message.html for more details.

然后还是找解决办法，终于发现这篇文章，
http://blog.csdn.net/keep_holding_on/article/details/76188657
尝试一波：
Mr.Smile填坑记——AndroidStudio3.0 Canary 8注解报错Annotation processors must be explicitly declared now.

体验最新版AndroidStudio3.0 Canary 8的时候，发现之前项目的butter knife报错，用到注解的应该都会报错

Error:Execution failed for task ':app:javaPreCompileDebug'.> Annotation processors must be explicitly declared now. The following dependencies on the compile classpath are found to contain annotation processor. Please add them to the annotationProcessor configuration. - butterknife-7.0.1.jar Alternatively, set android.defaultConfig.javaCompileOptions.annotationProcessorOptions.includeCompileClasspath = true to continue with previous behavior. Note that this option is deprecated and will be removed in the future. See https://developer.android.com/r/tools/annotation-processor-error-message.html for more details.

在app的build中android { ...
defaultConfig { ...

//添加如下配置就OK了

javaCompileOptions { annotationProcessorOptions { includeCompileClasspath = true } }

} ...
}

最后终于可以运行了！最后的最后，想用一首"凉凉的"送给android studio团队，你要让我们android开发者怎么样啊？虽说是升级，可是制造这么多麻烦真的好么？希望这篇文章能对各位有所帮助，继续努力喽！

作者：小小程序员jh
链接：https://www.jianshu.com/p/c04b97f8cc45
來源：简书
简书著作权归作者所有，任何形式的转载都请联系作者获得授权并注明出处。