龙目岛1.18.2引发transformClassesWithDexBuilderForDebug

Question

最近开始使用IntelliJ IDE。我试图在IntelliJ中打开一个Android项目，该项目是在Android Studio IDE中构建的。但这导致了许多问题。无法解决的问题之一是transformClassesWithDexBuilderForDebug。

我已经尝试了所有可能的dex问题解决方案，但似乎没有任何效果。

在研究--stacktrace时发现了这一点

错误处理C：\ Users \ prath.gradle \ caches \ modules-2 \ files-2.1 \ org.projectlombok ** lombok ** \ 1.18.2 \ 524e0a697e9d62950b2f763d88d35cd8dc82a9a1 \ lombok-1.18.2.jar java.lang。RuntimeException 在org.objectweb.asm.ClassReader.readModule（ClassReader.java:731）在org.objectweb.asm.ClassVisitor.visitModule（ClassVisitor.java:148）在org.objectweb.asm.ClassReader.accept（ClassReader.java:632） ），位于com.android.builder.desugaring.DesugaringClassAnalyzer.analyze（DesugaringClassAnalyzer.java:144）的org.objectweb.asm.ClassReader.accept（ClassReader.java:500）上，com.android.builder.desugaring.DesugaringClassAnalyzer.analyzeJar（ com.android.builder.desugaring上的DesugaringClassAnalyzer.java:92）。com.android.build.gradle.internal.transforms.DesugarIncrementalTransformHelper.lambda $ GetInitalGraphData $ 4（DesugarInformer。 ），位于java.util.concurrent.ForkJoinTask $ AdaptedCallable.exec（ForkJoinTask.java：1448）在java.util.concurrent.ForkJoinTask.doExec（ForkJoinTask.java:290）在java.util.concurrent.ForkJoinPool $ WorkQueue.topLevelExec（ForkJoinPool.java:1020）在java.util.concurrent.ForkJoinPool.scan（ForkJoinPool .java：1656），位于java.util.concurrent.ForkJoinPool.runWorker（ForkJoinPool.java:1594），位于java.util.concurrent.ForkJoinWorkerThread.run（ForkJoinWorkerThread.java:177）

任务：app：transformClassesWithDexBuilderForDebug失败的java.lang.RuntimeException：java.base / jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0（Native方法）处的java.lang.RuntimeException java.base / jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance（NativeConstructorAccessorImpl.java:62 ）的java.base / jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance（DelegatingConstructorAccessorImpl.java:45）的java.base / java.lang.reflect.Constructor.newInstance（Constructor.java:490）的java.base / java。 java.base / java.util.concurrent.ForkJoinTask.reportException（ForkJoinTask.java:678）上的util.concurrent.ForkJoinTask.getThrowableException（ForkJoinTask.java:600）在java.base / java.util.concurrent.ForkJoinTask.join（ ForkJoinTask.java:722），位于com.android.ide.common.internal.WaitableExecutor。com.android.build.gradle.internal.transforms.DesugarIncrementalTransformHelper.getInitalGraphData（DesugarIncrementalTransformHelper.java:162）的com.android.build.gradle.internal.transforms.DesugarIncremental（WaitableExecutor.java:146）的com.android.build.gradle.internal.transforms.DesugarIncremental（ java：130），位于com.google.common.base.Suppliers $ NonSerializableMemoizingSupplier.get（Suppliers.java:160），位于com.android.build.gradle.internal.transforms.DesugarIncrementalTransformHelper.getDependenciesPaths（DesugarIncrementalTransformHelper.com:java:231） android.build.gradle.internal.transforms.DexArchiveBuilderTransform.getD8DesugaringCacheInfo（DexArchiveBuilderTransform.java:461）位于com.android.build.gradle.internal.transforms.DexArchiveBuilderTransform。在com.android.build.gradle.internal.pipeline.TransformTask $ 2.call（TransformTask.java:239）处转换com.android.build.gradle.internal.pipeline.TransformTask $ 2.call（DexArchiveBuilderTransform.java:375） java的com.android.builder.profile.ThreadRecorder.record（ThreadRecorder.java:102）的TransformTask.java:235）java的com.android.build.gradle.internal.pipeline.TransformTask.transform（TransformTask.java:230）的Http java.base / jdk.internal.reflect.NativeMethodAccessorImpl.invoke（NativeMethodAccessorImpl.java:62）的.base / jdk.internal.reflect.NativeMethodAccessorImpl.invoke0（java.base / jdk.internal.reflect.DelegatingMethodAccessorImpl。 org.gradle.internal.reflect.JavaMethod上的java.base / java.lang.reflect.Method.invoke（Method.java:566）上的invoke（DelegatingMethodAccessorImpl.java:43）。在org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute（StandardTaskAction.org.gradle.api.internal.project.taskfactory.IncrementalTask​​Action.doExecute（IncrementalTask​​Action.java:50）处调用（JavaMethod.java:73） 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） ）的org.gradle.internal.operations.DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute（DefaultBuildOperationExecutor.java:300），位于org.gradle.internal.operations.DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute（DefaultBuildOperationExorgor。 Operations.DefaultBuildOperationExecutor。在org.gradle.internal.operations.DefaultBuildOperationExecutor.run（DefaultBuildOperationExecutor.java:90）在org.gradle.internal.operations.DelegatingBuildOperationExecutor.run（DelegatingBuildOperationExecutor.java:31）处执行（DefaultBuildOperationExecutor.java:174） org.gradle.api.internal上的.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction（ExecuteActionsTaskExecuter.java:120）在org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions（ExecuteActionsTaskExecuter.java:99）在org.gradle.api.internal org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute（OutputDirectoryCreatingTaskExecuter.java:51）上的.tasks.execution.ExecuteActionsTaskExecuter.execute（ExecuteActionsTaskExecuter.java:77）在org.gradle.api.internal.tasks.execution上。在org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute（ResolveTaskOutputCachingStateExecuter.java:54）处的SkipUpToDateTaskExecuter.execute（SkipUpToDateTaskExecuter.java:59）在org.gradle.api.internal.tasks.execution.ValidatingTask处在org.gradle.api.internal.tasks.execution.FinalizeInputFilePropertiesTaskExecuter.execute（FinalizeInputFilePropertiesTaskExecuter.execute（FinalizeInputFilePropertiesTaskExecuter.execute。 44）在org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute（CleanupStaleOutputsExecuter.java:91）在org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute（ResolveTaskArtifactStateTaskExecuter.java：62）在org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute（SkipOnlyIfTaskExecuter.java:54）在org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute（SkipTaskWithNoActionsExecuter.java:59） org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute（CatchExceptionTaskExecuter.java:34）上的.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute（ExecuteAtMostOnceTaskExecuter.java:43）在org.gradle.api org.gradle.internal.operations.DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute（DefaultBuildOperationExecutor.java:300）上的.internal.tasks.execution.EventFiringTaskExecuter $ 1.run（EventFiringTaskExecuter.java:51）在org.gradle.internal.operations.DefaultBuild RunnableBuildOperationWorker。在org.gradle.internal.operations.DefaultBuildOperationExecutor.run（DefaultBuildOperationExecutor.java:90）在org.gradle.internal.operations.DefaultBuildOperationExecutor.execute（DefaultBuildOperationExecutor.java:174）在org.gradle.internal.operations.DefaultBuildOperationExecutor.run（DefaultBuildOperationExecutor.java:90）在org.gradle org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute（EventFiringTaskExecuter.java:46）上的.internal.operations.DelegatingBuildOperationExecutor.run（DelegatingBuildOperationExecutor.java:31）在org.gradle.execution.taskgraph.LocalTask​​InfoExecutor。 （LocalTask​​InfoExecutor.java:42），位于org.gradle.execution.taskgraph.DefaultTaskExecutionGraph $ BuildOperationAwareWorkItemExecutor.execute（DefaultTaskExecutionGraph.java:277），位于org.gradle.execution.taskgraph。org.gradle.execution.taskgraph.DefaultTaskPlanExecutor $ ExecutorWorker $ 1.execute（DefaultTaskPlanExecutor.java:135）的DefaultTaskExecutionGraph $ BuildOperationAwareWorkItemExecutor.execute（DefaultTaskExecutionGraph.java:262）在org.gradle.execution.taskgraph $ 1。在org.gradle.execution.taskgraph.DefaultTaskPlanExecutor $ ExecutorWorker.execute（DefaultTaskPlanExecutor.java:200）处的org.gradle.execution.taskgraph.DefaultTaskPlanExecutor $ ExecutorWorker.executeWithWork（DefaultTaskPlanExecutor.java:191）处的DefaultTaskPlanExecutor.java:130） org.gradle.execution.taskgraph.DefaultTaskPlanExecutor.process（DefaultTaskPlanExecutor.java:74）上的.gradle.execution.taskgraph.DefaultTaskPlanExecutor $ ExecutorWorker.run（DefaultTaskPlanExecutor.java:130）在org.gradle.execution处。org.gradle.execution.Default.exeBuildion.DefaultBuildExecuter.execute（DefaultBuildExecuter.java:40）的org.gradle.execution.SelectedTaskExecutionAction.execute（SelectedTaskExecutionAction.java:40）的taskgraph.DefaultTaskExecutionGraph.execute（DefaultTaskExecutionGraph.java:143） org.gradle.execution.DefaultBuildExecuter $ 1.proceed（DefaultBuildExecuter.java:46）的org.gradle.execution.DryRunBuildExecutionAction.execute（DryRunBuildExecutionAction.java:49）的.execution.DefaultBuildExecuter.access $ 000（DefaultBuildExecuter.java:24） org.gradle.initialization.DefaultGradleLauncher $ ExecuteTasks.run（DefaultGradleLauncher.java： 355）。在org.gradle.internal.operations.DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute（DefaultBuildOperationExecutor.java:292）在org.gradle.inoperation。 org.gradle.internal.operations.DefaultBuildOperationExecutor.run（DefaultBuildOperationExecutor.java:90）的org.gradle.internal.operations.DelegatingBuildOperationExecutor.run（DelegatingBuildOperationExecutor.java:31）的org.gradle.internal.operations.DefaultBuildOperationExecutor.run（DefaultBuildOperationExecutor.java:90） org.gradle.initialization中的.DefaultGradleLauncher.runTasks（DefaultGradleLauncher.java:219），位于org.gradle.initialization中的DefaultGradleLauncher.doBuildStages（DefaultGradleLauncher.java:149）。org.gradle.internal.invocation.GradleBuildController $ 1.call（GradleBuildController.java:77）的DefaultGradleLauncher.executeTasks（DefaultGradleLauncher.java:124）org.gradle.internal.invocation.GradleBuildController $ 1.call（GradleBuildController.java:74）在org.gradle.internal.work.StopShieldingWorkerLeaseService.withLocks（StopShieldingWorkerLeaseService.java:38）的org.gradle.internal.work.StopShieldingWorkerLeaseService.withLocks（StopShieldingWorkerLeaseService.java:38）的org.gradle.internal.invocation.GradleBuildController.doBuild （GradleBuildController.java:96）位于org.gradle.internal.invocation.GradleBuildController.run（GradleBuildController.java:74）位于org.gradle.tooling.internal.provider.runner.ClientProvidedBuildActionRunner.run（ClientProvidedBuildActionRunner.java:68） org.gradle.launcher.exec。org.gradle.launcher.exec.ChainingBuildActionRunner.run（ChainingBuildActionRunner.java:35）位于org.gradle.tooling.internal.provider.ValidatingBuildActionRunner.run（ValidatingBuildActionRunner.java:32）上的ChainingBuildActionRunner.run（ChainingBuildActionRunner.java:35）在org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner $ 3.run（RunAsBuildOperationBuildActionRunner.java:50）在org.gradle.internal.operations.DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute（DefaultBuildOperationExecutor.java:300）在org.gradlein。位于org.gradle.internal.operations的DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute（DefaultBuildOperationExecutor.java:292），位于org.gradle.internal.operations的DefaultBuildOperationExecutor.execute（DefaultBuildOperationExecutor.java:174）。位于org.gradle.internal.operations.DelegatingBuildOperationExecutor.run（DelegatingBuildOperationExecutor.java:31）的DefaultBuildOperationExecutor.run（DefaultBuildOperationExecutor.java:90）位于org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner.run（RunAsBuildOperation45）的org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner.run org.gradle.launcher.exec.InProcessBuildActionExecuter $ 1.transform（InProcessBuildActionExecuter.java:47）的org.gradle.launcher.exec.InProcessBuildActionExecuter $ 1的.gradle.tooling.internal.provider.SubscribableBuildActionRunner.run（SubscribableBuildActionRunner.java:51） org.gradle.composite.internal.DefaultRootBuildState.run（DefaultRootBuildState.java:79）的org.gradle.launcher.exec.InProcessBuildActionExecuter.execute（InProcessBuildActionExecuter.java）的.transform（InProcessBuildActionExecuter.java:44）：44）在org.gradle.launcher.exec.InProcessBuildActionExecuter.java（30）在org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute（BuildTreeScopeBuildActionExecuter.java:39）在org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute（ContinuousBuildActionExecuter.java:80）的org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute（ContinuousBuildActionExecuter.java:53的.execute（BuildTreeScopeBuildActionExecuter.java:25） ）在org.gradle.tooling.internal.provider.ServicesSetupBuildActionExecuter.execute（ServicesSetupBuildActionExecuter.java:62）上的org.gradle.tooling.internal.provider.ServicesSetupBuildActionExecuter.execute（ServicesSetupBuildActionExecuter.java:62）34）在org.gradle.tooling的org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute（GradleThreadBuildActionExecuter.java:25）的org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute（GradleThreadBuildActionExecuter.java:36） org.gradle.tooling.internal.provider.ParallelismConfigurationBuildActionExecuter.execute（ParallelismConfigurationBuildActionExecuter.java:29）处的.internal.provider.ParallelismConfigurationBuildActionExecuter.execute（ParallelismConfigurationBuildActionExecuter.java:43）在org.gradle.tooling.internalsprovid.ExecuteParent （org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute（StartParamsValidatingActionExecuter.java:31）位于org.gradle.tooling（StartParamsValidatingActionExecuter.java:59）。在org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute（SessionFailureReportingActionExecuter.java:44）处的内部.provider.SessionFailureReportingActionExecuter.execute（SessionFailureReportingActionExecuter.java:59）在org.gradle.tooling.internal.provider.Setuputeging（ org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute（SetupLoggingActionExecuter.java:30）上的SetupLoggingActionExecuter.java:46）org.gradle.launcher.daemon.server.exec.ExecuteBuild.doBuild（ExecuteBuild.java:67）在org.gradle.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.WatchForDisconnection。在org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute（ResetDeprecationLogger.org.org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed（DaemonCommandExecution.java:122）处执行（WatchForDisconnection.java:37） java：26）位于org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed（DaemonCommandExecution.java:122）位于org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon.execute（RequestStopIfSingleUsedDaemon.java:34）在org.org.gradle.launcher.daemon.server.exec.ForwardClientInput $ 2.call（ForwardClientInput.java:74）在org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed（DaemonCommandExecution.java:122）在org.org。 gradle.launcher.daemon.server.exec.ForwardClientInput $ 2.call（ForwardClientInput.java:72）位于org.gradle.util.Swapper.swap（Swapper。org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute（ForwardClientInput.java:72）处的org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed（DaemonCommandExecution.java:122）的java：38）在org.gradle.launcher.daemon.server.exec.LogAndCheckHealth.execute（LogAndCheckHealth.java:55）在org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed（DaemonCommandExecution.java:122） org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute（BuildCommandOnly.java:36）上的.launcher.daemon.server.exec.LogToClient.doBuild（LogToClient.java:62）在org.gradle.launcher.daemon上位于org.gradle.launcher.daemon.server.exec.BuildBuildEnvironment.doBuild（EstablishmentBuildEnvironment.java的.server.api.DaemonCommandExecution.proceed（DaemonCommandExecution.java:122）81）在org.org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute（BuildCommandOnly.java:36）在org.org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed（DaemonCommandExecution.java:122） .gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy $ 1.run（StartBuildOrRespondWithBusy.java:50）at org.gradle.launcher.daemon.server.DaemonStateCoordinator $ 1.run（DaemonStateCoordinator.java:295）at org.gradle.internal org.gradle.internal.concurrent.ManagedExecutorImpl $ 1.run（ManagedExecutorImpl.java:46）上的.concurrent.ExecutorPolicy $ CatchAndRecordFailures.onExecute（ExecutorPolicy.java:63）在java.base / java.util.concurrent.ThreadPoolExecutor.runWorker（ org中的java.base / java.util.concurrent.ThreadPoolExecutor $ Worker.run（ThreadPoolExecutor.java:628）中的ThreadPoolExecutor.java:1128）。gradle.internal.concurrent.ThreadFactoryImpl $ ManagedThreadRunnable.run（ThreadFactoryImpl.java:55）在java.base / java.lang.Thread.run（Thread.java:834）由以下原因引起：org.objectweb上的java.lang.RuntimeException。 org.objectweb.asm.ClassReader.readModule（ClassReader.java:731）的org.objectweb.asm.ClassReader.accept（ClassReader.java:632）的asm.ClassVisitor.visitModule（ClassVisitor.java:148） com.android.builder.desugaring.DesugaringClassAnalyzer.analyze（DesugaringClassAnalyzer.java:144）上的.asm.ClassReader.accept（ClassReader.java:500）在com.android.builder.desugaring.DesugaringClassAnalyzer.analyzeJar（DesugaringClassAnalyzer.java： ），位于com.android.build.gradle.internal.transforms的com.android.builder.desugaring.DesugaringClassAnalyzer.analyze（DesugaringClassAnalyzer.java:63）上。位于java.base / java.util.concurrent.ForkJoinTask $ AdaptedCallable.exec（ForkJoinTask.java:1448）的DesugarIncrementalTransformHelper.lambda $ getInitalGraphData $ 4（DesugarIncrementalTransformHelper.java:150）在java.base / java.util.concurrent.ForkJoinTask.do （ForkJoinTask.java:290）在java.base / java.util.concurrent.ForkJoinPool $ WorkQueue.topLevelExec（ForkJoinPool.java:1020）在java.base / java.util.concurrent.ForkJoinPool.scan（ForkJoinPool.java:1656） ）的java.base / java.util.concurrent.ForkJoinPool.runWorker（ForkJoinPool.java:1594）的java.base / java.util.concurrent.ForkJoinWorkerThread.run（ForkJoinWorkerThread.java:177）java.base / java.util.concurrent.ForkJoinPool $ WorkQueue.topLevelExec（ForkJoinPool.java:1020）上的base / java.util.concurrent.ForkJoinTask.doExec（ForkJoinTask.java:290）。 java.base / java.util.concurrent.ForkJoinPool.runWorker（ForkJoinPool.java:1594）上的parallel.ForkJoinPool.scan（ForkJoinPool.java:1656）在java.base / java.util.concurrent.ForkJoinWorkerThread.run（ForkJoinWorkerThread。 Java：177）java.base / java.util.concurrent.ForkJoinPool $ WorkQueue.topLevelExec（ForkJoinPool.java:1020）上的base / java.util.concurrent.ForkJoinTask.doExec（ForkJoinTask.java:290）。 java.base / java.util.concurrent.ForkJoinPool.runWorker（ForkJoinPool.java:1594）上的parallel.ForkJoinPool.scan（ForkJoinPool.java:1656）在java.base / java.util.concurrent.ForkJoinWorkerThread.run（ForkJoinWorkerThread。 Java：177）Java：177）Java：177）

它说：*出了什么问题：
任务'：app：transformClassesWithDexBuilderForDebug'的执行失败。
com.android.build.api.transform.TransformException：java.lang.RuntimeException：java.lang.RuntimeException

我该如何解决？

我已在设置中启用“注释”，Lombok已更新，清理并重建了N次，无效并重新启动。

Answer 1

试试这个gradle.properties：

  android.enableD8.desugaring = true
  android.enableIncrementalDesugaring = false

为我工作