天天看點

Android Studio 3.1.+(Gradle4.4) Build Sync Err: Unable to resolve dependency for*constraint-layout*

第一次安裝Android Studio 3.1.*建立項目build編譯成功,由于某種原因重裝該版本後建立空白項目build Sync意外失敗了:

Android Studio 3.1.+(Gradle4.4) Build Sync Err: Unable to resolve dependency for*constraint-layout*

網上搜尋解決方案一大堆,逐一測試一番統統失敗。其中有buildTypes缺失sourceSets{}的。

打開Project Structure Settings檢視預設配置,發現關鍵配置為空:

Android Studio 3.1.+(Gradle4.4) Build Sync Err: Unable to resolve dependency for*constraint-layout*

于是關鍵的配置如SDK, Compile Tools, JDK source和target均選擇最新版本:

Android Studio 3.1.+(Gradle4.4) Build Sync Err: Unable to resolve dependency for*constraint-layout*

修改後build.gradle(Module:app)的變化為(紫色字型):

Android Studio 3.1.+(Gradle4.4) Build Sync Err: Unable to resolve dependency for*constraint-layout*

編譯還是不通過。檢視Settings配置gradle,使用Android Studio預設的gradle版本,并且不勾選offline work,使用網絡下載下傳dependency依賴配置。

Android Studio 3.1.+(Gradle4.4) Build Sync Err: Unable to resolve dependency for*constraint-layout*

重新Build編譯,然後是漫長的等待,約莫5-6min的樣子也沒結果:既不報錯,也沒提示build成功。于是取消編譯,檢視gradle.properties配置,其中隻有一個預設的配置

# Specifies the JVM arguments used for the daemon process.
# The setting is particularly useful for tweaking memory settings.
org.gradle.jvmargs=-Xmx1024m
           

考慮到機器的實際情況,把參數org.gradle.jvmargs的值修改一下

Android Studio 3.1.+(Gradle4.4) Build Sync Err: Unable to resolve dependency for*constraint-layout*

這裡把“1024m”改成了“768m”

結果build終于很快通過:

Android Studio 3.1.+(Gradle4.4) Build Sync Err: Unable to resolve dependency for*constraint-layout*

注意:這隻是一個空白項目,前一個步驟編譯使用超過5min都沒有完成,這裡隻用了1min 15 sec。

Unable to resolve dependency part 1

繼續閱讀