安装的“旧”的Android Studio项目 - Studio更新后,将不再开/编译要求甚至更新的版本?

问题描述 投票:0回答:2

它一直是我上次碰到我的Android Studio项目的一年。所以,当我打开Android Studio中,我要求更新。之后,我得到一个错误的Gradle(我需要更新的版本),所以我更新...但现在我得到:

摇篮同步失败:此版本的Android工作室无法打开此项目,请与Android 3.5工作室或更新重试。 (4M 47号第83毫秒)

但是 - 因为我是用3.0版本和3.1更早,现在使用3.3几乎不能是真实的

所以......在“建设同步”我看到旁边的错误

建立项目参数化模型“com.android.builder.model.AndroidProject”“:应用程序”

细节:

了java.lang.RuntimeException:这个版本的Android工作室无法打开此项目,请与Android 3.5工作室或更新重试。在com.android.build.gradle.internal.ide.StudioVersions.verifyStudioIsNotOld(StudioVersions.kt:50)在com.android.build.gradle.internal.ide.StudioVersions.verifyStudioIsNotOld(StudioVersions.kt:30)在com.android .build.gradle.internal.ide.ModelBuilder.buildAndroidProject(ModelBuilder.java:319)在com.android.build.gradle.internal.ide.ModelBuilder.buildAll(ModelBuilder.java:222)在com.android.build.gradle .internal.ide.ModelBuilder.buildAll(ModelBuilder.java:138)在org.gradle.tooling.provider.model.internal.DefaultToolingModelBuilderRegistry $ ParameterizedBuildOperationWrappingToolingModelBuilder $ 1 $ 1。创建(DefaultToolingModelBuilderRegistry.java:138)在org.gradle.api.internal .project.DefaultProjectStateRegistry.withLenientState(DefaultProjectStateRegistry.java:132)在org.gradle.tooling.provider.model.internal.DefaultToolingModelBuilderRegistry $ ParameterizedBuildOperationWrappingToolingModelBuilder $ 1.call(DefaultToolingModelBuilderRegistry.java:134)在org.gradle.internal.operations.D efaultBuildOperationExecutor $ CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:315)在org.gradle.internal.operations.DefaultBuildOperationExecutor $ CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:305)在org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java: 175)在org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:101)在org.gradle.internal.operations.DelegatingBuildOperationExecutor.call(DelegatingBuildOperationExecutor.java:36)在org.gradle.tooling.provider.model .internal.DefaultToolingModelBuilderRegistry $ ParameterizedBuildOperationWrappingToolingModelBuilder.buildAll(DefaultToolingModelBuilderRegistry.java:131)在org.gradle.tooling.internal.provider.runner.DefaultBuildController.getParameterizedModel(DefaultBuildController.java:99)在org.gradle.tooling.internal.provider.runner .DefaultBuildController.getModel(DefaultBuildController.ja VA:81)在org.gradle.tooling.internal.consumer.connection.InternalBuildActionAdapter $ 2.getModel(InternalBuildActionAdapter.java:77)在org.gradle.tooling.internal.consumer.connection.BuildControllerAdapter.getModel(BuildControllerAdapter.java:62 )在com.android.tools.idea.gradle.project.sync.ng.SyncModuleModels.findParameterizedAndroidModel(SyncModuleModels.java:90)在com.android.tools.idea.gradle.project.sync.ng.SyncModuleModels.populate(SyncModuleModels的.java:63)在com.android.tools.idea.gradle.project.sync.ng.SyncProjectModels.populateModelsForModule(SyncProjectModels.java:119)在com.android.tools.idea.gradle.project.sync.ng.SyncProjectModels .populateModelsForModule(SyncProjectModels.java:123)在com.android.tools.idea.gradle.project.sync.ng.SyncProjectModels.populate(SyncProjectModels.java:86)在com.android.tools.idea.gradle.project.sync .ng.SyncAction.execute(SyncAction.java:59)在com.android.tools.idea.gradle.project.sync.ng.SyncAction.execute(SyncAction.java:33)在org.gradle .tooling.internal.consumer.connection.InternalBuildActionAdapter.execute(InternalBuildActionAdapter.java:80)在org.gradle.tooling.internal.provider.runner.ClientProvidedBuildActionRunner $ ResultBuildingListener.buildResult(ClientProvidedBuildActionRunner.java:114)在org.gradle.tooling .internal.provider.runner.ClientProvidedBuildActionRunner $ ResultBuildingListener.buildFinished(ClientProvidedBuildActionRunner.java:106)在sun.reflect.NativeMethodAccessorImpl.invoke0(本机方法)在sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)在sun.reflect .DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)在java.lang.reflect.Method.invoke(Method.java:497)在org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)在有机gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)在org.gradle.internal.event.DefaultListenerManager $ ListenerDetails.dispatch(DefaultListenerManager.java:376)在组织.gradle.internal.event.DefaultListenerManager $ ListenerDetails.dispatch(DefaultListenerManager.java:358)在org.gradle.internal.event.AbstractBroadcastDispatch.dispatch(AbstractBroadcastDispatch.java:58)在org.gradle.internal.event.DefaultListenerManager $ EventBroadcast $ ListenerDispatch.dispatch(DefaultListenerManager.java:346)在org.gradle.internal.event.DefaultListenerManager $ EventBroadcast $ ListenerDispatch.dispatch(DefaultListenerManager.java:333)在org.gradle.internal.event.AbstractBroadcastDispatch.dispatch(AbstractBroadcastDispatch.java :42)在org.gradle.internal.event.BroadcastDispatch $ SingletonDispatch.dispatch(BroadcastDispatch.java:230)在org.gradle.internal.event.BroadcastDispatch $ SingletonDispatch.dispatch(BroadcastDispatch.java:149)在org.gradle。 internal.event.AbstractBroadcastDispatch.dispatch(AbstractBroadcastDispatch.java:58)在org.gradle.internal.event.BroadcastDispatch $ CompositeDispatch.dispatch(BroadcastDispatch.java:324)在org.gradle.internal.event.BroadcastDis补丁$ CompositeDispatch.dispatch(BroadcastDispatch.java:234)在org.gradle.internal.event.ListenerBroadcast.dispatch(ListenerBroadcast.java:140)在org.gradle.internal.event.ListenerBroadcast.dispatch(ListenerBroadcast.java:37)在org.gradle.internal.dispatch.ProxyDispatchAdapter $ DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)在com.sun.proxy。$ Proxy13.buildFinished(来源不明)在org.gradle.initialization.DefaultGradleLauncher.finishBuild(DefaultGradleLauncher.java :179)在org.gradle.initialization.DefaultGradleLauncher.finishBuild(DefaultGradleLauncher.java:141)在org.gradle.internal.invocation.GradleBuildController $ 3.创建(GradleBuildController.java:83)在org.gradle.internal.invocation.GradleBuildController在在澳org.gradle.internal.work.StopShieldingWorkerLeaseService.withLocks(StopShieldingWorkerLeaseService.java:40)在org.gradle.internal.work.DefaultWorkerLeaseService.withLocks $ 3.创建(GradleBuildController.java:75)(DefaultWorkerLeaseService.java:183) rg.gradle.internal.invocation.GradleBuildController.doBuild(GradleBuildController.java:75)在org.gradle.internal.invocation.GradleBuildController.configure(GradleBuildController.java:64)在org.gradle.tooling.internal.provider.runner。 ClientProvidedBuildActionRunner.run(ClientProvidedBuildActionRunner.java:57)在org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)在org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)在组织.gradle.launcher.exec.BuildOutcomeReportingBuildActionRunner.run(BuildOutcomeReportingBuildActionRunner.java:58)在org.gradle.tooling.internal.provider.ValidatingBuildActionRunner.run(ValidatingBuildActionRunner.java:32)在org.gradle.launcher.exec.BuildCompletionNotifyingBuildActionRunner.run (BuildCompletionNotifyingBuildActionRunner.java:39)在org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner $ 3.call(RunAsBuildOperationBuildActionRunner.java:49)在org.gradle.launcher.exec.Run AsBuildOperationBuildActionRunner $ 3.call(RunAsBuildOperationBuildActionRunner.java:44)在org.gradle.internal.operations.DefaultBuildOperationExecutor $ CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:315)在org.gradle.internal.operations.DefaultBuildOperationExecutor $ CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java :305)在org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:175)在org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:101)在org.gradle.internal.operations。 DelegatingBuildOperationExecutor.call(DelegatingBuildOperationExecutor.java:36)在org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner.run(RunAsBuildOperationBuildActionRunner.java:44)在org.gradle.launcher.exec.InProcessBuildActionExecuter $ 1.transform(InProcessBuildActionExecuter.java:49)在org.gradle.launcher.exec.InProcessBuildActionExecuter $ 1.transform(的InPro cessBuildActionExecuter.java:46)在org.gradle.composite.internal.DefaultRootBuildState.run(DefaultRootBuildState.java:78)在org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:46)在org.gradle.launcher .exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:31)在org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute(BuildTreeScopeBuildActionExecuter.java:42)在org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute(BuildTreeScopeBuildActionExecuter.java:28 )在org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:78)在org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:52)在org.gradle.tooling。 internal.provider.SubscribableBuildActionExecuter.execute(SubscribableBuildActionExecuter.java:59)在org.gradle.tooling.internal.provider.SubscribableBuildActionExecuter.execute(Subscribab leBuildActionExecuter.java:36)在org.gradle.tooling.internal.provider.SessionScopeBuildActionExecuter.execute(SessionScopeBuildActionExecuter.java:68)在org.gradle.tooling.internal.provider.SessionScopeBuildActionExecuter.execute(SessionScopeBuildActionExecuter.java:38)在组织.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:37)在org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:26)在org.gradle.tooling.internal.provider .ParallelismConfigurationBuildActionExecuter.execute(ParallelismConfigurationBuildActionExecuter.java:43)在org.gradle.tooling.internal.provider.ParallelismConfigurationBuildActionExecuter.execute(ParallelismConfigurationBuildActionExecuter.java:29)在org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java :60)在org.gradle.tooling.internal.provider.StartParamsValidatingActio nExecuter.execute(StartParamsValidatingActionExecuter.java:32)在org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:55)在org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java: 41)在org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:48)在org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:32)在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:104)在org.gradle.launcher.daemon.server.exec.WatchForDisconnection.execute(WatchForDisconnection.java:37)在org.gradle.launcher.daemon.server.api.DaemonCommandExecution .proceed(DaemonCommandExecution.java:104)在org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute(ResetDeprecationLogger.java:26)在org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution的.java:104)在org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon.execute(RequestStopIfSingleUsedDaemon.java:34)在org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104 )在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.util.Swapper.swap(Swapper.java:38)在org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute(ForwardClientInput.java:72)在org.gradle.launcher.daemon.server。 api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)在org.gradle.launcher.daemon.server.exec.LogAndCheckHealth.execute(LogAndCheckHe alth.java:55)在org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)在org.gradle.launcher.daemon.server.exec.LogToClient.doBuild(LogToClient.java: 62)在org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)在org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)在有机.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:81)在org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)在org.gradle.launcher .daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)在org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy $ 1.run(StartBuildOrRespondWithBusy.java:50)在org.gradle.launcher.daemon。在org.gradle.internal.concurrent.ExecutorPolicy $ CatchAndRecordFailures.onExecu server.DaemonStateCoordinator $ 1.run(DaemonStateCoordinator.java:295) TE(ExecutorPolicy.java:63)在org.gradle.internal.concurrent.ManagedExecutorImpl $ 1.run(ManagedExecutorImpl.java:46)在java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)在java.util中。 concurrent.ThreadPoolExecutor $ Worker.run(ThreadPoolExecutor.java:617)在org.gradle.internal.concurrent.ThreadFactoryImpl $ ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)在java.lang.Thread.run(Thread.java:745)

此外,我注意到,在我的

女:\ Android的工作室项目\ sharedid \程序\的build.gradle我定义各种产品的味道。然而,没有出现在左窗格中的“生成变种”。我希望这是因为它已经在同步/解析莫名其妙地失败...

java android android-studio gradle android-gradle
2个回答
1
投票

请检查项目的gradle级别里面的gradle的版本

改变这种

     classpath 'com.android.tools.build:gradle:3.3.0'

到相应的版本


1
投票

请尝试如下

  • 文件>的Invalidate缓存/重新启动
  • 删除文件夹.gradle
  • 重新启动的Android工作室/重新导入项目
  • 重建和清理项目
© www.soinside.com 2019 - 2024. All rights reserved.