Android studio 如何修复';AAPT2内部异常:AAPT2';在TeamCity上通过gradle build步骤构建android项目时出错?

Android studio 如何修复';AAPT2内部异常:AAPT2';在TeamCity上通过gradle build步骤构建android项目时出错?,android-studio,gradle,android-gradle-plugin,teamcity,Android Studio,Gradle,Android Gradle Plugin,Teamcity,我已经在我的电脑上安装了TeamCity 2019.1,在Android项目上测试CI/CD。但我在仅在TeamCity中构建项目时面临以下问题: [10:23:22] [Step 1/3] > Task :app:mergeDebugResources FAILED [10:23:24] [Step 1/3] Execution failed for task ':app:mergeDebugResources'. com.android.ide.common.workers.Wor

我已经在我的电脑上安装了TeamCity 2019.1,在Android项目上测试CI/CD。但我在仅在TeamCity中构建项目时面临以下问题:

[10:23:22]  [Step 1/3] > Task :app:mergeDebugResources FAILED
[10:23:24]  [Step 1/3] Execution failed for task ':app:mergeDebugResources'. com.android.ide.common.workers.WorkerExecutorException: 8 exceptions were raised by workers:
com.android.builder.internal.aapt.v2.Aapt2InternalException: AAPT2 aapt2-3.4.1-5326820-windows Daemon #0: Daemon startup failed
这个问题与我的问题类似,但在这种情况下,错误发生在Android Studio中:[问题]:

在Android Studio中,该项目运行良好。我尝试从Github签出这个项目,并运行
gradlew clean build
构建它,它对我来说也很好

在生成日志之后:


有没有关于如何解决这个问题的猜测?

您需要给出构建机器上安装的SDK的路径

检查此线程的答案

以下是解决方案:

  • Ctrl+Alt+Suppr打开任务管理器

  • 杀死所有“Java(TM)平台SE二进制”进程

  • react本地运行的android


但系统知道SDK的安装位置。系统将在默认位置进行搜索。如果您的SDK不在默认位置,那么您需要将此告知gradle build system。您的链接指向与Linux相关的解决方案。这是针对Windows TeamCity生成代理的。什么是“默认位置”?再说一次,如果gradle找不到Android SDK,我不知道AAPT2会是什么样子。你解决过这个问题吗?我在2017年TC上有一个类似的问题。另外,你的堆栈溢出链接已经死了。你解决了吗?@TalShani遗憾的是没有解决。@JonathanGiorgiSilveira那么你最终做了什么?您是如何使用team city构建应用程序的?
[10:23:24]  [Step 1/3] Execution failed for task ':app:mergeDebugResources'. com.android.ide.common.workers.WorkerExecutorException: 8 exceptions were raised by workers:
com.android.builder.internal.aapt.v2.Aapt2InternalException: AAPT2 aapt2-3.4.1-5326820-windows Daemon #0: Daemon startup failed
This should not happen under normal circumstances, please file an issue if it does.
com.android.builder.internal.aapt.v2.Aapt2InternalException: AAPT2 aapt2-3.4.1-5326820-windows Daemon #5: Daemon startup failed
This should not happen under normal circumstances, please file an issue if it does.
com.android.builder.internal.aapt.v2.Aapt2InternalException: AAPT2 aapt2-3.4.1-5326820-windows Daemon #6: Daemon startup failed
This should not happen under normal circumstances, please file an issue if it does.
com.android.builder.internal.aapt.v2.Aapt2InternalException: AAPT2 aapt2-3.4.1-5326820-windows Daemon #3: Daemon startup failed
This should not happen under normal circumstances, please file an issue if it does.
com.android.builder.internal.aapt.v2.Aapt2InternalException: AAPT2 aapt2-3.4.1-5326820-windows Daemon #4: Daemon startup failed
This should not happen under normal circumstances, please file an issue if it does.
com.android.builder.internal.aapt.v2.Aapt2InternalException: AAPT2 aapt2-3.4.1-5326820-windows Daemon #7: Daemon startup failed
This should not happen under normal circumstances, please file an issue if it does.
com.android.builder.internal.aapt.v2.Aapt2InternalException: AAPT2 aapt2-3.4.1-5326820-windows Daemon #2: Daemon startup failed
This should not happen under normal circumstances, please file an issue if it does.
com.android.builder.internal.aapt.v2.Aapt2InternalException: AAPT2 aapt2-3.4.1-5326820-windows Daemon #1: Daemon startup failed
This should not happen under normal circumstances, please file an issue if it does.
[10:23:23]  [Step 1/3] 
[10:23:23]  [Step 1/3] 10 actionable tasks: 9 executed, 1 up-to-date
[10:23:24]  [Step 1/3] Process exited with code 1
[10:23:24]  [Step 1/3] Gradle failure report
[10:23:24]  [Step 1/3] Process exited with code 1 (Step: gradle-build (Gradle))
[10:23:24]  [Step 1/3] Step gradle-build (Gradle) failed