OGeek|极客世界-中国程序员成长平台

标题: Android studio 3.0 报错，怎么解决？ [打印本页]

---

作者: 菜鸟教程小白    时间: 2022-12-9 06:49
标题: Android studio 3.0 报错，怎么解决？

我现在刚刚将我的 android studio 更新到 3.0，但是当我尝试在我的项目上构建 apk 时，它显示以下错误:

项目依赖于 com.google.android.support:wearable:2.0.0，因此它还必须依赖于(作为提供的依赖项)com.google.android.wearable:wearable:2.0.0

我的 build.gradle 是这样的:

dependencies {

    compile fileTree(include: ['*.jar'], dir: 'libs')
    compile project(':lpd')
    compile 'com.google.android.support:wearable:2.0.0-alpha2'
    compile 'com.google.android.gms:play-services-wearable:9.4.0'
    compile files('libs/zxing_2.3.0.jar')
    compile(name: 'hwwearableservice-release', ext: 'aar')
    compile 'com.google.android.gms:play-services-appindexing:9.4.0'
}

有什么问题吗？

---

Best Answer-推荐答案

根据新的 gradle dependency instruction compile 已被弃用，因此库使用 api 并使用最新的稳定库版本作为 2.1.0

而且由于该版本是稳定版本，所以

api 'com.google.android.support:wearable:2.1.0'

或者最好使用

implementation 'com.google.android.support:wearable:2.1.0'

---

实现

if an implementation dependency changes its API, Gradle recompiles only that dependency and the modules that directly depend on it. Most app and test modules should use this configuration.

api

When a module includes an api dependency, it's letting Gradle know that the module wants to transitively export that dependency to other modules, so that it's available to them at both runtime and compile time. This configuration behaves just like compile (which is now deprecated), and you should typically use this only in library modules. That's because, if an api dependency changes its external API, Gradle recompiles all modules that have access to that dependency at compile time

关于Android studio 3.0 报错，怎么解决？，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/47034454/

---

欢迎光临 OGeek|极客世界-中国程序员成长平台 (https://www.ogeek.cn/)

Powered by Discuz! X3.4