簡體 English 中英

在Android Studio虛擬設備中調試時出錯

[英]Error when debug in android studio virtual device

原文 2019-05-29 10:09:18 2 1 android/ android-studio/ android-emulator/ avd

在Android Emulator中使用debug時，出現錯誤：

java.lang.RuntimeException：java.lang.RuntimeException：java.io.FileNotFoundException：D：\\ Android \\ androiddtudio_project \\ vitrin-android \\ app \\ build \\ intermediates \\ instant_run_split_apk_resources \\ debug \\ instantRunSplitApkResourcesDebug \\ out \\ slice_6 \\ resourcelect_ap在sun。位於sun.reflect的.NativeConstructorAccessorImpl.newInstance0（本地方法），位於sun.reflect.DelegatingConstructorAccessorImpl.newInstance（DelegatingConstructorAccessorImpl.java:45）處的sun.reflect.NativeConstructorAccessorImpl.newInstance（NativeConstructorAccessorImpl.java:62） .java：423），位於java.util.concurrent.ForkJoinTask.getThrowableException（ForkJoinTask.java:593），位於java.util.concurrent.ForkJoinTask.reportException（ForkJoinTask.java:677），位於java.util.concurrent.ForkJoinTask.join（在com.android.ide.common.internal.WaitableExecutor.waitForTasksWithQuickFail（WaitableExecutor.java:149）處的com.android.build.gradle.internal.transforms.InstantRunSliceSplitApkBuilde上的ForkJoinTask.java:720） r.transform（InstantRunSliceSplitApkBuilder.java:246）在com.android.build.gradle.internal.pipeline.TransformTask $ 2.call（TransformTask.java:239）在com.android.build.gradle.internal.pipeline.TransformTask $ 2。在com.android.build.gradle.internal.pipeline.TransformTask.transform（TransformTask.java:230）處調用com.android.builder.profile.ThreadRecorder.record（ThreadRecorder.java:102）處的（TransformTask.java:235）在org.gradle.internal上的java.lang.reflect.Method.invoke（Method.java:498）上的sun.reflect.DelegatingMethodAccessorImpl.invoke（DelegatingMethodAccessorImpl.java:43）上的sun.reflect.GeneratedMethodAccessor85.invoke（未知源） org.gradle.api.internal.project.taskfactory.IncrementalTaskAction.doExecute（IncrementalTaskAction.java:47）的.reflect.JavaMethod.invoke（JavaMethod.java:73）org.gradle.api.internal.project.taskfactory.StandardTaskAction的.reflect.JavaMethod.invoke（JavaMethod.java:73）或位於org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute（StandardTaskAction.java:28）的.execute（StandardTaskAction.java:41） g.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter $ 2.run（ExecuteActionsTaskExecuter.java:284）在org.gradle.internal.operations.DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute（DefaultBuildOperationExecutor.java:301）在org.gradle.internal org.gradle.internal.operations.DefaultBuildOperationExecutor.execute（DefaultBuildOperationExecutor.java:175）上的org.gradle.internal.operations.DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute（DefaultBuildOperationExecutor.java:293）在org.gradle.internal.operations.DefaultBuildOperation ：91）在org.gradle的org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction（ExecuteActionsTaskExecuter.java:273）的org.gradle.internal.operations.DelegatingBuildOperationExecutor.run（DelegatingBuildOperationExecutor.java:31）處。 org.gradle.api.internal.tasks.ex上的api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions（ExecuteActionsTaskExecuter.java:258）在org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter $ TaskExecution.execute（ExecuteActionsTaskExecuter.java:145）處的ecution.ExecuteActionsTaskExecuter.access $ 200（ExecuteActionsTaskExecuter.java:67）在org.gradle.internal.execution.impl.steps org.gradle.internal.execution.impl.steps.TimeoutStep.executeWithoutTimeout處的org.gradle.internal.execution.impl.steps.CancelExecutionStep.execute（CancelExecutionStep.java:34）處的.ExecuteStep.execute（ExecuteStep.java:49）（TimeoutStep.java:69）在org.gradle.internal.execution.impl.steps.TimeoutStep.execute（TimeoutStep.java:49）在org.gradle.internal.execution.impl.steps.CatchExceptionStep.execute（CatchExceptionStep.java ：33）在org.gradle.internal.execution.impl.steps.CreateOutputsStep.execute（CreateOutputsStep.java:50）在org.gradle.internal.execution.impl.steps.SnapshotOutputStep.execute（SnapshotOutputStep.java:43）在org.gradle.internal.ex上的org.gradle.internal.execution.impl.steps.SnapshotOutputStep.execute（SnapshotOutputStep.java:29） org.gradle.internal.execution.impl.steps.CacheStep.lambda $ execute $ 3（CacheStep.java:83）處的ecution.impl.steps.CacheStep.executeWithoutCache（CacheStep.java:134）在java.util.Optional.orElseGet （Optional.java:267）在org.gradle.internal.execution.impl.steps.CacheStep.execute（CacheStep.java:82）在org.gradle.internal.execution.impl.steps.CacheStep.execute（CacheStep.java ：36），位於org.gradle.internal.execution.impl.steps.StoreSnapshotsStep.execute（StoreSnapshotsStep.java:38）的org.gradle.internal.execution.impl.steps.PrepareCachingStep.execute（PrepareCachingStep.java:33）處org.gradle上的org.gradle.internal.execution.impl.steps.StoreSnapshotsStep.execute（StoreSnapshotsStep.java:23）位於org.gradle.internal.execution.impl.steps.SkipUpToDateStep.executeBecause（SkipUpToDateStep.java:96）在org.gradle。 org.gradle.internal.execution.impl.steps.SkipUpToDateStep的internal.execution.impl.steps.SkipUpToDateStep.lambda $ execute $ 0（SkipUpToDateStep.java:89）位於java.util.Optional.map（Optional.java:215） .execute（SkipUpToDat org.gradle.internal.execution.impl.steps.SkipUpToDateStep.execute（SkipUpToDateStep.java:36）處的eStep.java:52）org.gradle.internal.execution.impl.DefaultWorkExecutor.execute（DefaultWorkExecutor.java:34）處的在org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute（ExecuteActionsTaskExecuter.java:91）在org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute（ResolveTaskOutputCachingStateExecuter.java:91）在org.gradle org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute（SkipEmptySourceFilesTaskExecuter.java:119）上的.api.internal.tasks.execution.ValidatingTaskExecuter.execute（ValidatingTaskExecuter.java:57）在org.gradle.api.internal上org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute（CleanupStaleOutputsExecuter.java:93）上的.tasks.execution.ResolvePreviousStateExecuter.execute（ResolvePreviousStateExecuter.java:43）在org.gradle.api.internal.tasks.execution .FinalizePropertiesTaskExecuter.exec org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute（FinalizePropertiesTaskExecuter.java:45）在org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute（ResolveTaskArtifactStateTaskExecuter.java:94）在org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute java：56）位於org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute（SkipOnlyIfTaskExecuter.java:55）位於org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute（CatchExceptionTaskExecuter.java:36） org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter $ 1.executeTask（EventFiringTaskExecuter.java:67）org.org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter $ 1.call（EventFiringTaskExecuter.java:52） org.gradle.internal.operations.DefaultBuildOperationExecutor $ CallableBuildOperationWorker.execute（DefaultBuildOperationExecutor.java:315）上的.gradle.api.internal.tasks.execution.EventFiringTaskExecuter $ 1.call（EventFiringTaskExecuter.java:49） org.gradle.internal.operations.DefaultBuildOperation的.internal.operations.DefaultBuildOperationExecutor $ CallableBuildOperationWorker.execute（DefaultBuildOperationExecutor.java:305）在org.gradle.internal.operations.DefaultBuildOperationExecutor.execute（DefaultBuildOperationExecutor.java:175）在org.gradle.internal.operations.DefaultBuildOperation .java：101），位於org.org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute（EventFiringTaskExecuter.java:49），位於org.gradle.internal.operations.DelegatingBuildOperationExecutor.call（DelegatingBuildOperationExecutor.java：36）。在org.gradle.execution.taskgraph.DefaultTaskExecutionGraph $ InvokeNodeExecutorsAction.execute（DefaultTaskExecutionGraph.java:355）處的gradle.execution.plan.LocalTaskNodeExecutor.execute（LocalTaskNodeExecutor.java:43）在org.gradle.execution.Taskgraph.DefaultTaskInecution在org.gradle.execution.taskgraph.DefaultTaskExecutionGraph $ BuildOperationAware上執行（DefaultTaskExecutionGraph.java:343） org.gradle.execution.taskgraph.DefaultTaskExecutionGraph $ BuildOperationAwareExecutionAction.execute（DefaultTaskExecutionGraph.java:322）的ExecutionAction.execute（DefaultTaskExecutionGraph.java:336）在org.gradle.execution.plan.DefaultPlanExecutor $ ExecutorWorker（$ 1。：134），位於org.gradle.execution.plan.DefaultPlanExecutor $ ExecutorWorker $ 1.execute（DefaultPlanExecutor.java:129），位於org.gradle.execution.plan.DefaultPlanExecutor $ ExecutorWorker $ 1.execute（DefaultPlanExecutor.java:129） org.gradle.execution.plan.DefaultPlanExecutor $ ExecutorWorker.run（DefaultPlanExecutor.java:129）上的.execution.plan.DefaultPlanExecutor $ ExecutorWorker.executeNextNode（DefaultPlanExecutor.java:193）org.gradle.internal.concurrent.ExecutorPolicy $ CatchAndRecordF org.gradle.internal.concurrent.ManagedExecutorImpl $ 1.run（ManagedExecutorImpl.java:46）的java.util.concurrent.ThreadPoolExecutor.runWorker（ThreadPoolExecutor.java:1142）的.onExecute（ExecutorPolicy.java:63） org.gradle.internal.concurrent.ThreadFactoryImpl $ ManagedThreadRunnable.run（ThreadFactoryImpl.java:55）上的va.util.concurrent.ThreadPoolExecutor $ Worker.run（ThreadPoolExecutor.java:617）在java.lang.Thread.run（Thread。 java：745）由以下原因引起：java.lang.RuntimeException：java.io.FileNotFoundException：D：\\ Android \\ androiddtudio_project \\ vitrin-android \\ app \\ build \\ intermediates \\ instant_run_split_apk_resources \\ debug \\ instantRunSplitApkResourcesDebug \\ out \\ slice_6 \\ resources_ap在java。 util.concurrent.ForkJoinTask $ AdaptedCallable.exec（ForkJoinTask.java:1431）at java.util.concurrent.ForkJoinTask.doExec（ForkJoinTask.java:289）at java.util.concurrent.ForkJoinPool $ WorkQueue.runTask（ForkJoinPool.java： 1056）at java.util.concurrent.ForkJoinPool.runWorker（ForkJoinPool.java:1692）at java.util.concurrent.ForkJoinWorkerThread.run（ForkJoinWorkerThread.java:157）原因：java.io.FileNotFoundException：D：\\ Android \\ androiddtudio_project \\ vitrin-的Android \\程序\\編譯\\中間體\\ instant_run_split_apk_resources \\調試\\瞬間 java.util.concurrent.ForkJoinTask。（Adapted。 1424）...還有4個