gradlew assembleDebug --debug
[DEBUG] [org.gradle.launcher.daemon.server.Daemon] DaemonExpirationPeriodicCheck running
[DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
[DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
[DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
方法1 不起作用
尝试了stackoverflow上面的各种方法,比如删除./gradle文件夹,gradle开离线模式,开启gradle daemon等等,都没有作用。
因为是在upload阶段出现的错误,我也想过是不是因为代理设置出的问题。我尝试把as的代理设置关掉了,ss开全局模式,这个问题还是没有解决。
最后我在gradle.properties这个文件下面发现了下面几行有关代理的设置:
systemProp.http.proxyHost=127.0.0.1
systemProp.http.proxyPort=1080
删除这两行代码之后果然成功解决了上面的问题
方法2 有点用
Thanks for your much appreciated help. I solved this issue. Apparently the issue was because (I suppose that) the JaCoCo was dexing along with my class dexing and was issuing a locks. I fixed this by removing the testCoverageEnabled=true line in my app’s build.gradle.
In case any of you guys run into similar issue. Create two build flavours (prod and development) and add the line testCoverageEnable=true only for development flavor and set it to false else where. Also ensure that your development has the minSdkVersion set to 21 (Lollipop) as the dexing is done for ART and basically you won’t be running into this issue.
- 去除多渠道
- 多版本都加入 testCoverageEnable=true
方法3 说是内存问题,似乎没啥用
Android Studio: Unable to start the daemon process
If You just open too much applications in Windows and make the Gradle have no enough memory in Ram to start the daemon process.So when you come across with this situation,you can just close some applications such as iTunes and so on. Then restart your android studio.
File Menu - > Invalidate Caches/ Restart->Invalidate and Restart.
或者?
- Try deleting your .gradle from C:\Users\ directory and try again.
或者
if you are on windows,
Try deleting your .gradle from C:\Users\ directory and try again.
or
go to Android Studio -> Preferences -> Gradle -> and tick Offline work.