如何解決Android Studio 3.2上的此錯誤

Question

com.google.common.util.concurrent.SettableFuture@ea15b8f [狀態= PENDING>

org.gradle.execution.MultipleBuildFailures：構建完成，但有1個失敗。

在org.gradle.initialization.DefaultGradleLauncher $ ExecuteTasks.run（DefaultG radleLauncher.java:358）

在org.gradle.internal.operations.DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute（DefaultBuildOperationExecutor.java：org.gradle.internal.operations.DefaultBuildOperationExecutor $ RunnableBuil dOperationWorker.execute（DefaultBuildOperationExecutor.java:300）處org.gradle.internal.operations.DelegatingBuildOperationExecutor.run（31）上的org.gradle.internal.operations.DefaultBuildOperationExecutor.run（DefaultBuildOperationExecutor.java:90）上的Operations.DefaultBuildOperationExecutor.execute（DefaultBuildOperationExecutor.java:174）在org.gradle.initialization.DefaultGradleLauncher.runTasks（DefaultGradleLauncher.java:219）在org.gradle.initialization.DefaultGradleLauncher.doBuildStages（DefaultGradleLauncher.java:149）在org.gradle.initialization.DefaultGradleLauncher.executeTasks（DefaultGradleLauncher.java ）在org.gradle.internal.invocation.GradleBuildController $ 1.call（GradleBuildController.java:77）在org org.gradle.internal.work.StopShieldingWorkerLeaseService.withLocks（.org.gradle.internal.invocation.GradleBuildController $ 1.call（GradleBuildController.java:74）在org.gradle.internal.work.DefaultWorkerLeaseService.withLocks（DefaultWorkerLeaseService.java:154） org.gradle.internal.invocation.GradleBuildController.doBuild（GradleBuildController.java:96）的StopShieldingWorkerLeaseService.java:38）org.gradle.tooling的org.gradle.internal.invocation.GradleBuildController.run（GradleBuildController.java:74）的StopShieldingWorkerLeaseService.java:38） org.gradle.launcher.exec.ChainingBuildActionRunner.run（ChainingBuildActionRunner.java:35）上的.internal.provider.runner.BuildModelActionRunner.run（BuildModelActionRunner.java:55）org.gradle.launcher.exec.ChainingBuildActionRunner.run（ChainingBuildActionRunner .java：35），位於org.gradle.tooling.internal.provider.ValidatingBuildActionRunner.run（ValidatingBuildActionRunner.java：32），位於org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner $ 3.run（RunAsBuildOperationBuildActionRunner.java:5） 0）在org.gradle.internal.operations.DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute（DefaultBuildOperationExecutor.java:292.org：org.gradle.internal.operations.DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute（DefaultBuildOperationExecutor.java:300）在org.gradle.internal.operations.DelegatingBuildOperationExecutor.java（31： ）在org.gradle.launcher.exec的org.gradle.tooling.internal.provider.SubscribableBuildActionRunner.run（SubscribableBuildActionRunner.java:51）的org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner.run（RunAsBuildOperationBuildActionRunner.java:45）處。 InProcessBuildActionExecuter $ 1.transform（InProcessBuildActionExecuter.java:47）在org.gradle.launcher.exec.InProcessBuildAction org.gradle.composite.internal.DefaultRootBuildState.run（DefaultRootBuildState.java:79）的Executer $ 1.transform（InProcessBuildActionExecuter.java:44）org.gradle.launcher.exec.InProcessBuildActionActionExecuter.execute（InProcessBuildActionExecuter.java:44） org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute（BuildTreeScopeBuildActionExecuter.java:39）的org.gradle.launcher.exec.InProcessBuildActionExecuter.execute（InProcessBuildActionExecuter.java:30）org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute（ org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute（ContinuousBuildActionExecuter.java:80）處BuildTreeScopeBuildActionExecuter.java:25）org.orgle.tooling.internal.provider.ContinuousBuildActionExecuter.execute（ContinuousBuildActionExecuter.java:53）處org.gradle.tooling.internal.provider.ServicesSetupBuildActi上的.gradle.tooling.internal.provider.ServicesSetupBuildActionExecuter.execute（ServicesSetupBuildActionExecuter.java:62） org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute（GradleThreadBuildActionExecuter.java： 25）在org.gradle.tooling的org.gradle.tooling.internal.provider.ParallelismConfigurationBuildActionExecuter.execute（ParallelismConfigurationBuildActionExecuter.java:29）的org.gradle.tooling.internal.provider.ParallelismConfigurationBuildActionExecuter.execute（ParallelismConfigurationBuildActionExecuter.java:43） org.gradle.tooling.Executeing.executeAction.executeAction.internal.provider.org上的.internal.provider.StartParamsValidatingActionExecuter.execute（StartParamsValidatingActionExecuter.java:59）位於org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute（StartParamsValidatingActionExecuter.java:31） （SessionFailureReportingActionExecuter.java:59）在org.gradle.to org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute（SetupLoggingActionExecuter.java:46）上的oling.internal.provider.SessionFailureReportingActionExecuter.javaute（SessionFailureReportingActionExecuter.java:44）在org.gradle.launcher.daemon.server.exec.ExecuteBuild.doBuild（ExecuteBuild.java:67）處在org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute（BuildCommandOnly）處執行（SetupLoggingActionExecuter.java:30）。 java：36）位於org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed（DaemonCommandExecution.java:122）位於org.gradle.launcher.daemon.server.exec.WatchForDisconnection.execute（WatchForDisconnection.java:37）在org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed（DaemonCommandExecution.java:122）在org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute（ResetDeprecationLogger.java:26）在org.gradle .launcher.daemon.server.api.DaemonCommandExecution.p 在org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed（DaceCommandExecution.proceed（DaceCommandDaeCommand.java:122）在org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon.execute（RequestStopIfSingleUsedDaemon.java:34） org.gradle.launcher.daemon.server.exec.ForwardClientInput $ 2.call（ForwardClientInput.java:74）處org.gradle.launcher.daemon.server.exec.ForwardClientInput $ 2.call（ForwardClientInput.java： 72）位於org.gradle.launcher.daemon的org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute（ForwardClientInput.java:72）的org.gradle.util.Swapper.swap（Swapper.java:38） org.gradle.launcher.daemon.server.exec.LogAndCheckHealth.execute（LogAndCheckHealth.java:55）上的.server.api.DaemonCommandExecution.proceed（DaemonCommandExecution.java:122）在org.gradle.launcher.daemon.server.api位於org.grale.org.gradle.launcher.daemon.server.exec.LogToClient.doBuild（LogToClient.java:62）的.DaemonCommandExecution.proceed（DaemonCommandExecution.java:122） org.gradle.launcher上的dle.launcher.daemon.server.exec.BuildCommandOnly.execute（BuildCommandOnly.java:36）位於org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed（DaemonCommandExecution.java:122）。位於org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute（BuildCommandOnly.java:36）處的daemon.server.exec.BuildBuildEnvironment.doBuild（BuildBuildEnvironment.java:81）位於org.gradle.launcher.daemon.server處。 org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy $ 1.run（StartBuildOrRespondWithBusy.java:50）上的api.DaemonCommandExecution.proceed（DaemonCommandExecution.java:122）在org.gradle.launcher.daemon.server.DaemonStateCoordator在org.gradle.internal.concurrent.ManagedExecutorImpl $ 1.run（ManagedExecutorImpl.java:46）的org.gradle.internal.concurrent.ExecutorPolicy $ CatchAndRecordFailures.onExecute（ExecutorPolicy.java:63）處運行（DaemonStateCoordinator.java:295） java.util中的java.util.concurrent.ThreadPoolExecutor.runWorker（ThreadPoolExecutor.java:1142）。 org.gradle.internal.concurrent.ThreadFactoryImpl $ ManagedThreadRunnable.run（ThreadFactoryImpl.java:55）處的並發ThreadPoolExecutor $ Worker.run（ThreadPoolExecutor.java:617）在java.lang.Thread.run（Thread.java:745）由以下原因引起：org.gradle.api.tasks.TaskExecutionException：任務'：app：mergeDebugResources'的執行失敗。 在org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions（ExecuteActionsTaskExecuter.java:110）在org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute（ExecuteActionsTaskExecuter.java:77）在org.gradle org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute（SkipUpToDateTaskExecuter.java:59）上的.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute（OutputDirectoryCreatingTaskExecuter.java:51）在org.gradle.api.in org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute（ValidatingTaskExecuter.java:59）位於org.gradle.api.internal.tasks.execution處的.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute（ResolveTaskOutputCachingStateExecuter.java:54） org.gradle.api.internal.tasks.execution.FinalizeInputFilePropertiesTaskExecuter.execute（FinalizeInputFilePropertiesTaskExecuter.java:44）處的.SkipEmptySourceFilesTaskExecuter.execute（SkipEmptySourceFilesTaskExecuter.java:101） org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute（ResolveTaskArtifactStateTaskExecuter.java:62）在org.gradle.api上的.api.internal.tasks.execution.CleanupStaleOutputsExecuter.java.91（CleanupStaleOutputsExecuter.java:91）。 org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute（SkipOnlyIfTaskExecuter.java:54）上的.tasks.execution.SkipTaskWithNoActionsExecuter.execute（SkipTaskWithNoActionsExecuter.java:59）在org.gradle.api.internal.task中在org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute（CatchExceptionTaskExecuter.java:34）處的ExecuteAtMostOnceTaskExecuter.execute（ExecuteAtMostOnceTaskExecuter.java:43）在org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter $ 1。在org.gradle.internal.operations.DefaultBuildOperationE處運行（EventFiringTaskExecuter.java:51）在org.gradle.internal.operations.DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute（DefaultBuildOperationExecutor.java:300） org.gradle.internal.operations.DefaultBuildOperationExecutor.execute（DefaultBuildOperationExecutor.java:174）處的xecutor $ RunnableBuildOperationWorker.execute（DefaultBuildOperationExecutor.java:292）在org.gradle.internal.operations.DefaultBuildOecationExecutor.run（DefaultBuild.OperationExecutor.90）：在org.gradle.execution.taskgraph上的org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute（EventFiringTaskExecuter.java:46）上的org.gradle.internal.operations.DelegatingBuildOperationExecutor.run（DelegatingBuildOperationExecutor.java:31） org.gradle.execution.taskgraph.DefaultTaskExecutionGraph $ BuildOperationAwareWorkItemExecutor.execute（DefaultTaskExecutionGraph.java:277）處的org.gradle.execution.taskgraph.DefaultTaskExecutionGrapher Graph.Build.execute（LocalTask​​InfoExecutor.java:42） ：262）at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor $ ExecutorWorker $ 1.execute（DefaultTaskPlanEx ecutor.java:135）at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor $ ExecutorWorker $ 1.execute（DefaultTaskPlanExecutor.java:130）at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor $ ExecutorWorker.execute（DefaultTaskPlanExecutor.java:200） org.gradle.execution.taskgraph上的org.gradle.execution.taskgraph.DefaultTaskPlanExecutor $ ExecutorWorker.executeWithWork（DefaultTaskPlanExecutor.java:191）位於org.gradle.execution.taskgraph.DefaultTaskPlanExecutor $ ExecutorWorker.run（DefaultTaskPlanExecutor.java:130）處。 org.gradle.execution.SelectedTaskExecutionAction.execute（SelectedTaskExecutionAction.execute（SelectedTaskExecutionAction.java:40）處的org.gradle.execution.taskgraph.DefaultTaskExecutionGraph.execute（DefaultTaskExecutionGraph.java:143）處的DefaultTaskPlanExecutor.process（DefaultTaskPlanExecutor.java:74） org.gradle.execution.DefaultBuildExecuter.access $ 000（DefaultBuildExecuter.java:24）處的org.gradle.execution.DefaultBuildExecuter $ 1.p的.execution.DefaultBuildExecuter.execute（DefaultBuildExecuter.java:40） 在org.gradle.execution.roceed（DefaultBuildExecuter.java:46）在org.gradle.execution.DryRunBuildExecutionAction.execute（DryRunBuildExecutionAction.java:49）在org.gradle.execution.DefaultBuildExecuter.execute（DefaultBuildExecuter.java:40）在org.gradle.execution.DefaultBuildExecuter org.gradle.initialization.DefaultGradleLauncher $ ExecuteTasks.run（DefaultGradleLauncher.java:355）處的.execute（DefaultBuildExecuter.java:33）... 77更多原因：org.gradle.internal.UncheckedException：java.util.concurrent。 ExecutionException：com.android.builder.internal.aapt.v2.Aapt2InternalException：AAPT2 aapt2-3.2.1-4818971-windows守護程序＃0：守護程序啟動失敗這種情況在正常情況下不應該發生，如果存在，請提出問題。 org.gradle.internal.UncheckedException.throwAsUncheckedException（UncheckedException.java:63）org.gradle.internal.UncheckedException.throwAsUncheckedException（UncheckedException.java:40）org.gradle.internal.reflect.JavaMethod.invoke（JavaMethod.java） ：76）在org.gradle.api.internal.project.taskfactory.IncrementalTask​​Action.doExecute（IncrementalTask​​Action.java:50）在org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute（StandardTaskAction.java:39）在org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute（StandardTaskAction.java:26）at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter $ 1.run（ExecuteActionsTaskExecuter.java:131）at org.gradle org.gradle的.internal.operations.DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute（DefaultBuildOperationExecutor.java:300）在org.gradle.internal.operations.DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute（DefaultBuildOperationExecutor.java:292）在org.gradle。 org.gradle.internal.operations.DelegatingBuildOperationExecutor.run（31）上的org.gradle.internal.operations.DefaultBuildOperationExecutor.run（DefaultBuildOperationExecutor.java:90）上的ons.DefaultBuildOperationExecutor.execute（DefaultBuildOperationExecutor.java:174）在org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction（ExecuteActionsTaskExecuter.java:120）在org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions（ExecuteActionsTaskExecuter.java:99）... 115更多原因：java.util.concurrent.ExecutionException：com.android.builder.internal.aapt.v2.Aapt2InternalException：AAPT2 aapt2-3.2.1-4818971-windows守護程序＃0：守護程序啟動失敗在正常情況下不應發生這種情況，請提出問題。 在com.android.ide.common.workers.ExecutorServiceAdapter.close（ExecutorServiceAdapter.kt：56）在java.util.concurrent.ForkJoinTask.get（ForkJoinTask.java:1006）在com.android.build.gradle.internal.aapt位於com.android.build.gradle.tasks.MergeResources.doFullTask​​Action（MergeResources.java:324）的.WorkerExecutorResourceCompilationService.close（WorkerExecutorResourceCompilationService.kt：67）位於com.android.build.gradle.internal.tasks.IncrementalTask​​.taskAction（Incremental .java：106），位於sun.reflect.NativeMethodAccessorImpl.invoke0（本機方法），位於java.sun.reflect.DelegatingMethodAccessorImpl.invoke（DelegatingMethodAccessorImpl.java:43），位於sun.reflect.NativeMethodAccessorImpl.invoke（NativeMethodAccessorImpl.java:62）。 org.gradle.internal.reflect.JavaMethod.invoke（JavaMethod.java:73）處的lang.reflect.Method.invoke（Method.java:498）... 126個以上原因：com.android.builder.internal.aapt .v2.Aapt2InternalException：AAPT2 aapt2-3.2.1-4818971-windows守護程序＃0：守護程序啟動失敗這應該 通常情況下不會發生此問題，請提出問題。 在com.android.builder.internal.aapt.v2.Aapt2Daemon.handleError（Aapt2Daemon.kt：148）在com.android.builder.internal.aapt.v2.Aapt2Daemon.checkStarted（Aapt2Daemon.kt：57）在com.android。 com.android.builder.internal.aapt.v2.Aapt2DaemonManager $ LeasedAaptDaemon.compile（Aapt2DaemonManager.kt：170）上的.builder.internal.aapt.v2.Aapt2Daemon.compile（Aapt2Daemon.kt：79）在com.android.build上.gradle.internal.res.Aapt2CompileWithBlameRunnable $ run $ 1.invoke（Aapt2CompileWithBlameRunnable.kt：37）位於com.android.build.gradle.internal.res.Aapt2CompileWithBlameRunnable $ run $ 1.invoke（Aapt2CompileWithBlameRunnable。 com.android.build.gradle.internal.res.namespaced.Aapt2DaemonManagerService.useAaptDaemon $ default（Aapt2DaemonManagerService.kt：69）上的.build.gradle.internal.res.namespaced.Aapt2DaemonManagerService.useAaptDaemon（Aapt2DaemonManagerService.kt：71） .com.android.ide.common.work上的.android.build.gradle.internal.res.Aapt2CompileWithBlameRunnable.run（Aapt2CompileWithBlameRunnable.kt：34） ers.ExecutorServiceAdapter $ submit $ submission $ 1.run（ExecutorServiceAdapter.kt：39）at java.util.concurrent.ForkJoinTask $ AdaptedRunnableAction.exec（ForkJoinTask.java:1386）at java.util.concurrent.ForkJoinTask.doExec（ForkJoinTask.java ：289）在java.util.concurrent.ForkJoinPool $ WorkQueue.runTask（ForkJoinPool.java:1056）在java.util.concurrent.ForkJoinPool.runWorker（ForkJoinPool.java:1692）在java.util.concurrent.ForkJoinWorkerThread.run（ ForkJoinWorkerThread.java:157）由以下原因引起：com.android.builder.internal.aapt.v2.Aapt2InternalException：無法啟動AAPT2進程AAPT2 aapt2-3.2.1-4818971-Windows Daemon＃0。 30秒內未准備好。 com.android.builder.internal.aapt.v2.Aapt2DaemonImpl.stopQuietly（Aapt2DaemonImpl.kt：122）com.android.builder.internal.aapt.v2.Aapt2DaemonImpl.startProcess（Aapt2DaemonImpl.kt：102）處.builder.internal.aapt.v2.Aapt2Daemon.checkStarted（Aapt2Daemon.kt：53）...抑制了13個以上：java.util.concurrent.TimeoutException：AAPT2 aapt2-3.2.1-4818971-windows Daemon＃0：失敗在30秒內關閉。 在com.android.builder.internal.aapt.v2.Aapt2DaemonImpl.stopQuietly（Aapt2DaemonImpl.kt：124）處的com.android.builder.internal.aapt.v2.Aapt2DaemonImpl.stopProcess（Aapt2DaemonImpl.kt：209）處強制關機。 。15更多原因：java.util.concurrent.TimeoutException：在com.google.common.util.concurrent.AbstractFuture.get上等待com.google.common.util.concurrent.SettableFuture@ea15b8f [status = PENDING] 30秒（AbstractFuture.java:442）在com.google.common.util.concurrent.AbstractFuture $ TrustedFuture.get（AbstractFuture.java:90）在com.android.builder.internal.aapt.v2.Aapt2DaemonImpl.startProcess（Aapt2DaemonImpl.kt ：100）...還有14個

Answer 1

在一個項目中，我一遍又一遍地面臨着同樣的問題。 我的gradle版本是gradle 4.6。 然后，后來我將android studio更新為3.4.1，當我開始有類似的錯誤日志時。 我將與項目同步的gradle更改為5.1.1。 現在工作正常。