blocks|key|151509|text|已通过转到Android+Studio+->+Preferences+->+Gradle+->和ticking+Offline+work修复此问题。仍然不知道哪里出了问题，但至少现在它可以编译了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|151510|编辑:在安卓工作室的新版本中，路径是File+->+Other+Settings+->+Default+Settings+->+Build-Excecution-Deployment+->+Gradle|151511|entityMap^0|5|E|N|B|12|6|1K|C|0|I|4|Q|E|18|G|1S|R|2N|6|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|I|$]]

Fixed it by going to <code>Android Studio</code> -> <code>Preferences</code> -> <code>Gradle</code> -> and ticking <code>Offline work</code>. Still have no idea what was wrong, but at least now it compiles.

Edit: 
In new Android Studio Versions the path is <code>File</code> -> <code>Other Settings</code> -> <code>Default Settings</code> -> <code>Build-Excecution-Deployment</code> -> <code>Gradle</code>

blocks|key|151513|text|这个问题似乎很陈旧，但以防有人需要它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|151514|最近，在安装了fresh+Ubuntu14.04之后，我就遇到了这个问题。在谷歌搜索了一段时间后，我没有幸运地检查终端，结果发现libz.so.1不见了。所以我安装了它，像魅力一样工作。|offset|length|style|BOLD|CODE|151515|此处安装说明：libz.so.1:+cannot+open+shared+object+file|151516|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/21256866/libz-so-1-cannot-open-shared-object-file^0|0|7|H|1S|9|0|7|15|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]|$D|W|E|X|F|H]]|9|@]|A|$]]|$1|I|3|J|5|6|7|Y|8|@]|9|@$D|Z|E|10|1|11]]|A|$]]|$1|K|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

The question seems old but in case anyone need it.

I have just faced this problem recently, after a fresh Ubuntu 14.04 installation.
After google for a while with no luck i checked the terminal, it turned out that <code>libz.so.1</code> is missing. So i installed it, worked like charm.

Installing instruction here:
<a href="https://stackoverflow.com/questions/21256866/libz-so-1-cannot-open-shared-object-file">libz.so.1: cannot open shared object file</a>

blocks|key|151518|text|您必须在文件中添加执行模式:+AndroidStudioProjects/YourProjectName/gradlew，这样Android+Studio才能执行它。如果您在linux机器上，请使用以下命令:+chmod+%2Bx+gradlew要运行此命令，您可能需要具有管理权限。在Ubuntu中，您可以使用sudo+chmod+%2Bx+gradlew来完成此操作|type|unstyled|depth|inlineStyleRanges|entityRanges|data|151519|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You have to add execution mode to the file: AndroidStudioProjects/YourProjectName/gradlew so that Android Studio can execute it.
if you are on a linux machine use this command: chmod +x gradlew
to run this command you may need to have administration privileges. in Ubuntu you can use sudo chmod +x gradlew to do that

blocks|key|147643|text|我在virtualbox+5.0.16虚拟机和带有Android+Studio+2.0的gradle版本2.10上安装了centos+7+64位|type|unstyled|depth|inlineStyleRanges|entityRanges|data|147644|gradle的日志文件位于$HOME/.gradle/daemon/2.10日志文件：daemon-<some+number>.out.log|offset|length|style|CODE|147645|通过检查这个日志文件，我发现aapt没有找到libz.so.1。|147646|尽管命令"locate+libz.so.1“的输出是|147647|/usr/lib64/libz.so
/usr/lib64/libz.so.1
/usr/lib64/libz.so.1.2.7|code-block|syntax|javascript|147648|aapt找不到它。|147649|为了解决这个问题，我不得不执行|147650|yum+install+zlib.i686|147651|在那之后，Gradle开始成为一个有魅力的人。祝好运!|147652|entityMap^0|0|D|P|17|S|0|M|9|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@$D|12|E|13|F|G]|$D|14|E|15|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|16|8|@$D|17|E|18|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|19|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|1A|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|1B|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1C|8|@]|9|@]|A|$]]|$1|U|3|V|5|N|7|1D|8|@]|9|@]|A|$O|P]]|$1|W|3|X|5|6|7|1E|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|Z|$]]

I have centos 7 64 bits installed on a virtualbox 5.0.16 virtual machine and gradle version 2.10 with Android Studio 2.0 

The log file of gradle is located at <code>$HOME/.gradle/daemon/2.10</code>
Log file: <code>daemon-&lt;some number&gt;.out.log</code>

By inspecting this log file I found out that <code>libz.so.1</code> was not found by aapt.

Despite that command "locate libz.so.1" output was

<pre><code>/usr/lib64/libz.so
/usr/lib64/libz.so.1
/usr/lib64/libz.so.1.2.7
</code></pre>

aapt was not able to find it.

In order to solve the issue I had to execute

<pre><code>yum install zlib.i686
</code></pre>

After that Gradle started working as a charm.
Good luck!

blocks|key|2730339|text|我也有过类似的经历。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2730340|当我从命令运行gradle时，它会抛出这个异常|2730341|org.gradle.api.tasks.TaskExecutionException:+Execution+failed+for+task+':app:compileDevDebugJavaWithJavac'.|code-block|syntax|javascript|2730342|在排队等了大概25分钟后|2730343|:app:compileDevDebugJavaWithJavac|2730344|事实证明，这与我使用的android+annotations有关。我替换了|offset|length|2730345|@UiThread+|2730346|我使用的是|2730347|activity.runOnUiThread(new+Runnable(...|2730348|它开始编译得很好。这很奇怪，因为我在代码中的许多其他地方使用了@UiThread注释。|2730349|entityMap|0|LINK|mutability|MUTABLE|url|http://androidannotations.org/^0|0|0|0|0|0|B|J|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|18|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|19|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|1A|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|1B|8|@]|9|@$O|1C|P|1D|1|1E]]|A|$]]|$1|Q|3|R|5|F|7|1F|8|@]|9|@]|A|$G|H]]|$1|S|3|T|5|6|7|1G|8|@]|9|@]|A|$]]|$1|U|3|V|5|F|7|1H|8|@]|9|@]|A|$G|H]]|$1|W|3|X|5|6|7|1I|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]]]

I had something similar.

When I ran gradle from the command like it would throw this exception

<pre><code>org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':app:compileDevDebugJavaWithJavac'.
</code></pre>

after waiting at this line for like 25 minutes

<pre><code>:app:compileDevDebugJavaWithJavac
</code></pre>

it turned out to have something to do with the <a href="http://androidannotations.org/" rel="nofollow">android annotations</a> I was using. I replaced the 

<pre><code>@UiThread 
</code></pre>

I was using with 

<pre><code>activity.runOnUiThread(new Runnable(...
</code></pre>

And it started to compile just fine. Its weird because I was using the @UiThread annotation in lots of other places in my code.

blocks|key|2942806|text|从设置启用脱机工作|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2942807|​|2942808|📷|atomic|offset|length|2942809|2942810|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/abe5016d226bce60e2db1b5a0027d727.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

Enable Offline Work from Setting 

<a href="https://i.stack.imgur.com/FD306.png" rel="noreferrer"><img src="https://i.stack.imgur.com/FD306.png" alt="enter image description here"></a>

blocks|key|150392|text|在我的例子中，看起来gradle在64位的Ubuntu+16.04上缺少32位的库。执行sudo+apt-get+install+libstdc%2B%2B6:i386解决了问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|150393|entityMap^0|18|10|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

In my case looks like gradle was missing 32 bit library on a 64 bit Ubuntu 16.04. Doing <code>sudo apt-get install libstdc++6:i386</code> resolved the problem.

blocks|key|147664|text|在将google+play+api添加到依赖项{}之后，我遇到了这种情况。当我按照here的描述设置它时，./gradlew+app:assembleDebug显示了一个类似Dex+ID+limit+reached+use+multi-dex.的错误，我决定删除我最近添加的依赖项，这个问题就消失了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|147665|Google还建议使用proguard作为一种技术来优化同一文档中的索引ID的数量。|147666|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.android.com/studio/build/multidex.html^0|1H|R|2F|Z|15|4|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

This happened to me after adding google play api to dependencies{}. <code>./gradlew app:assembleDebug</code> showed an error saying something like <code>Dex ID limit reached use multi-dex.</code> just as I was setting it up as described <a href="https://developer.android.com/studio/build/multidex.html" rel="nofollow">here</a>, I decided to remove the dependency I recently added and the issue was gone. 

Google also suggests using proguard as a technique to optimize the number of Dex IDs in the same document.

blocks|key|148891|text|对于GNU/Linux用户：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|148892|我将SDK从另一个存储复制到我的主目录中。然后我得到了股票gradle+build+running。问题出在SDK文件的权限上。查看gradle控制台日志，如果您看到一些权限被拒绝的内容，则执行以下操作-通过以下命令授予所有文件执行权限：|offset|length|style|CODE|148893|chmod+-R+%2Bx+/path/to/android-sdk|148894|entityMap^0|0|T|K|0|0|W|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

For GNU/Linux Users:

I copied the SDK from another storage to my home directory. Then I was getting stock <code>gradle build running</code>. The problem was the permissions of SDK files. Watch the gradle console log and if you see some permission denieded stuff, then do the following - give all the files executing permission by this command:

<code>chmod -R +x /path/to/android-sdk</code>

blocks|key|2942960|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2942961|2942962|2942963|解决方案就是将变量SLAVE_AAPT_TIMEOUT添加到我的Windows环境中，并将其设置为30|2942964|entityMap^0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|G|7|@]|8|@]|9|$]]|$1|A|3|-4|4|5|6|H|7|@]|8|@]|9|$]]|$1|B|3|-4|4|5|6|I|7|@]|8|@]|9|$]]|$1|C|3|D|4|5|6|J|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|K|7|@]|8|@]|9|$]]]|F|$]]

In my case, I was getting this error by the Gradle Builder (Android Studio 2.2, Windows 10)

<blockquote>
 <code>java.lang.RuntimeException</code>: Timed out while waiting for slave aapt process, try setting environment variable <code>SLAVE_AAPT_TIMEOUT</code> to a value bigger than 5 seconds 
</blockquote>

The solution was just to add the variable SLAVE_AAPT_TIMEOUT to my Windows environment, and set it to 30

blocks|key|2730701|text|我也遇到过同样的问题，并解决了在系统变量中设置变量SLAVE_AAPT_TIMEOUT的问题，其值为30。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2730702|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I was with the same problem and solved setting variable SLAVE_AAPT_TIMEOUT in System Variables with the value 30.

blocks|key|2730719|text|发生这种情况的原因有很多。因此，这里有一些帮助隔离原因的步骤，而不是给出确切的修复方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2730720|2730721|从命令行运行gradle命令。它还会失败吗？|ordered-list-item|2730722|2730723|因此，使用$+./gradlew+myTask|offset|length|style|CODE|2730724|If标志重新运行。有什么有用的信息吗？|unordered-list-item|2730725|2730726|$+./gradlew+myTask+--debug|2730727|If它只是挂起了，尝试获取堆栈跟踪。在转储文件中搜索myTask|2730728|2730729|$+jps+-mv+%7C+grep+Gradle+<-确保使用大写"G“2290+GradleDaemon+3.3+-XX:MaxPermSize=512m+-XX:%2BHeapDumpOnOutOfMemoryError+-Xmx2304M+-Dfile.coding=UTF-8+-Duser.country=US+-Duser.language=en+-Duser.variant+$+jstack+-l+2290+>>+dump.txt+<-如果您的进程ID仅在运行Android+Studio时挂起，请为Android+Studio生成线程转储|2730730|2730731|2730732|entityMap^0|0|0|0|0|5|I|0|0|0|0|Q|0|Q|6|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|13|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|15|8|@$I|16|J|17|K|L]]|9|@]|A|$]]|$1|M|3|N|5|O|7|18|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1A|8|@$I|1B|J|1C|K|L]]|9|@]|A|$]]|$1|S|3|T|5|O|7|1D|8|@$I|1E|J|1F|K|L]]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1H|8|@]|9|@]|A|$]]|$1|X|3|-4|5|O|7|1I|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|10|$]]

This can happen for lots of reasons. So instead of giving an exact fix, here are some steps to help isolate the cause.

<ol>
<li>Run the gradle command from command line. Does it still fail?

<code>$ ./gradlew myTask</code></li>
<li>If so, re-run with debug flag. Any useful info? 

<code>$ ./gradlew myTask --debug</code></li>
<li>If it's just hanging, try getting a stack trace. Search the dump file for <code>myTask</code>

<pre><code>$ jps -mv | grep Gradle &lt;--- be sure to use capital "G"
2290 GradleDaemon 3.3 -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -Xmx2304M -Dfile.encoding=UTF-8 -Duser.country=US -Duser.language=en -Duser.variant
$ jstack -l 2290 &gt;&gt; dump.txt &lt;--- your process ID will be different
</code></pre></li>
<li>If it's only hanging when running Android Studio, generate thread dump for Android Studio <a href="https://developer.android.com/studio/report-bugs.html#thread-dump" rel="nofollow noreferrer">read more here</a>.</li>
</ol>

blocks|key|150503|text|我用的是Windows，我也遇到了同样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|150504|对我来说，gradlew可执行文件不知何故被删除了，不知道是怎么删除的。我在金丝雀上，我以前也遇到过这个问题。|150505|在Android+Studio的终端窗口中，输入gradlew，如果缺少，它将重新下载并安装它。(我以前的解决方案是完全重装Android+Studio，所以这更简单)|offset|length|style|CODE|150506|entityMap^0|0|0|O|7|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@$F|O|G|P|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

I'm on Windows, and I had the same problem. 

For me, the gradlew executable somehow got deleted, no idea how. I'm on the Canary, and I've had the issue before. 

In the terminal window on Android Studio, type <code>gradlew</code> and it will redownload and install it if it's missing. (My old solution was a complete reinstall of Android Studio, so this is easier)

blocks|key|2730744|text|经过大量的努力和遵循上面发布的所有解决方案(以及类似的帖子)，我终于发现我电脑上的问题是杀毒应用程序。我禁用了它，gradle刷新并快速构建，就像问题开始之前一样。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2730745|看起来我的杀毒软件最近开始阻止gradle从互联网上更新/下载必要的信息，这就是导致加载和刷新项目的延迟和最终超时的原因。每次禁用杀毒软件都会纠正这个问题。|2730746|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

After a lot of struggle and following all solutions posted above (and in similar posts) I finally found that the problem on my PC was the antivirus application. I disabled it and gradle refreshed and built fast, as it did before the problem started. 

It looks like my antivirus recently started blocking gradle from updating/downloading necessary information from the Internet and that is what is causing the delays and eventually timeouts in loading and refreshing a project. Disabling the antivirus it corrects the problem, every time.

blocks|key|2943036|text|我也有同样的问题，即使是新的标准项目(Ubuntu+16.04)。问题出现在Gradle的第三方依赖项中。查看文件：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2943037|~/.gradle/init.gradle|2943038|它可能包含Gradle无法加载的其他依赖项。您可以在控制台中看到无法加载的内容：|2943039|./gradlew+--debug|2943040|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I had the same problem, even with new standard projects (Ubuntu 16.04). The problem turned out to be in third-party dependencies of the Gradle. View the file: 
~/.gradle/init.gradle 
It may contain additional dependencies, which the Gradle can not load.
You can see what can not be loaded in the console: 
./gradlew --debug

blocks|key|2730791|text|如果您使用realm库并使用RealmStudio或RealmBrowser打开文件锁，请确保执行delete+file+.realm+/.realm和folder+.realm.management。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2730792|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you use realm library and use RealmStudio or RealmBrowser to open file .realm, make sure you perform delete file .realm/lock and folder .realm.management.

blocks|key|2943077|text|我认为java.exe是这个问题的原因。只需手动终止此应用程序并尝试。在使用Android+studio+3.0.1时，它对我来说真的很有效。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2943078|entityMap^0|3|8|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I think <code>java.exe</code> is the reason of this issue. Just manually kill this application and try. It really worked for me using Android studio 3.0.1.

blocks|key|147792|text|在我的例子中，它停留在mergeDebugResources上，因为我意外地在字符串中有一个双转义单引号的\\'。Android+Studio不会将此标记为错误，而是会卡住构建！|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|147793|entityMap^0|B|J|1H|3|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

In my case it was stuck on <code>mergeDebugResources</code> because I accidentally had a double-escaped single-quote <code>\\'</code> in a string. Android Studio doesn't mark this as an error, but instead gets stuck building!

Android Studio (Beta) 0.8.6 gets stuck when I try to build/run the project, as well as clean it. It stays responsive, but the Gradle: Executing Tasks message doesn't disappear (longer than 20 minutes is when I give up) and the app never runs.

This is what I attempted:

<ul>
<li>Invalidate caches/restart</li>
<li>Force quit and restart</li>
<li>Remove it from Applications (on Mac) and re-download it from the official website. </li>
</ul>

<img src="https://i.stack.imgur.com/r70AL.png" alt="enter image description here">

How to fix Android Studio getting stuck executing Gradle tasks?

Android Studio

日志文件

虚拟机

Android

Windows

Ubuntu

Linux

当我尝试构建/运行项目以及清理项目时，Android Studio (Beta) 0.8.6卡住了。它保持响应，但Gradle: Executing Tasks消息不会消失(超过20分钟是我放弃的时候)，应用程序永远不会运行。这就是我所尝试的：Invalidate caches/restartForce quit an...

问如何修复Android Studio在执行Gradle任务时遇到的问题？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何修复Android Studio在执行Gradle任务时遇到的问题？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何修复Android Studio在执行Gradle任务时遇到的问题？
EN