[email protected]: starting failing
Prerequisites
- [x] I have written a descriptive issue title.
- [x] I have searched all issues/PRs to ensure it has not already been reported or fixed.
- [x] I have verified that I am using the latest version of Scoop and corresponding bucket.
Package Name
android-studio
Expected/Current Behaviour
Expect the application to start, like previous versions. Instead get the error:
Internal error
com.intellij.ide.plugins.EssentialPluginMissingException: Missing essential plugins: com.intellij.modules.json
at com.intellij.ide.plugins.PluginManagerCore.checkEssentialPluginsAreAvailable(PluginManagerCore.kt:598)
at com.intellij.ide.plugins.PluginManagerCore.initializePlugins(PluginManagerCore.kt:671)
at com.intellij.ide.plugins.PluginManagerCore$initializeAndSetPlugins$2.invokeSuspend(PluginManagerCore.kt:870)
at com.intellij.ide.plugins.PluginManagerCore$initializeAndSetPlugins$2.invoke(PluginManagerCore.kt)
at com.intellij.ide.plugins.PluginManagerCore$initializeAndSetPlugins$2.invoke(PluginManagerCore.kt)
at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:62)
at kotlinx.coroutines.BuildersKt__Builders_commonKt.withContext(Builders.common.kt:163)
at kotlinx.coroutines.BuildersKt.withContext(Unknown Source)
at com.intellij.platform.diagnostic.telemetry.impl.TracerKt.span(tracer.kt:56)
at com.intellij.idea.Main$startApp$2$1$1.span(Main.kt:100)
at com.intellij.diagnostic.CoroutineTracerShim.span$default(CoroutineTracerShim.kt:31)
at com.intellij.ide.plugins.PluginManagerCore.initializeAndSetPlugins$intellij_platform_core_impl(PluginManagerCore.kt:868)
at com.intellij.ide.plugins.PluginDescriptorLoader$scheduleLoading$pluginSetDeferred$1.invokeSuspend(PluginDescriptorLoader.kt:403)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:608)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:873)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:763)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:750)
-----
JRE: 21.0.5+-12932927-b750.29 amd64 (JetBrains s.r.o.)
C:\Users\mock\scoop\apps\android-studio\2024.3.1.13\jbr
Tried resetting settings and plugins, didn't work
Steps to Reproduce
scoop install android-studio
Possible Solution
I don't know, but I suspect it's a packaging issue, since updating manually on my other system doesn't cause this error
Scoop and Buckets Version
Current Scoop version:
859d1db5 (HEAD -> master, tag: v0.5.2, origin/master, origin/HEAD) chore(release): Bump to version 0.5.2 (#6080)
'main' bucket:
7ba048c0d (HEAD -> master, origin/master, origin/HEAD) pnpm: Update to version 10.6.1
'extras' bucket:
c3f8eafb35 (HEAD -> master, origin/master, origin/HEAD) virtualhere-client: Update to version 5.8.6
'java' bucket:
fce6c6a9 (HEAD -> master, origin/master, origin/HEAD) temurin8-nightly-jre: Update to version 8.0.452-4.0.202503042156
Scoop Config
last_update scoop_repo scoop_branch
----------- ---------- ------------
2025/03/07 15:04:11 https://github.com/ScoopInstaller/Scoop master
PowerShell Version
Name Value
---- -----
PSVersion 7.5.0
PSEdition Core
GitCommitId 7.5.0
OS Microsoft Windows 10.0.22631
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Additional Softwares
No response
I noticed that I ended up with two different plugins folders after an update. One pointed to (as a junction/link) scoop\persist\android-studio\plugins an the other was a local folder plugins.original which contained the necessary files/libraries.
You can try to empty the plugins folder and move the files from plugins.original into plugins
or just:
- uninstall android studio:
scoop uninstall android-studio - remove your persist data:
scoop\persist\android-studio - install android studio again:
scoop install android-studio
I had the same problem and it was resolved with the method crra mentioned. Thanks.
I had the same error for version 2025.1.2.11. I fixed this with @crra method.
Can't the installer handle the deletion of the plugins directory in persist?
Or at least update the notes section so people are aware of what to do after installing.
Hello, everyone.
I’d like to fix this issue, but I’m not a user of this software. To avoid unnecessary maintenance in the future, I’d like to ask a question — could you please reply when you have time?
After installing android-studio and running some tests, I found that user settings and manually installed plugins are stored in $env:APPDATA\Google\AndroidStudio<version>.
I’d like to confirm whether any user-installed plugins might also be stored in the $dir\plugins folder. Additionally, should the contents of the $dir\modules directory be persisted?
Hello, everyone.
I’d like to fix this issue, but I’m not a user of this software. To avoid unnecessary maintenance in the future, I’d like to ask a question — could you please reply when you have time?
After installing
android-studioand running some tests, I found that user settings and manually installed plugins are stored in$env:APPDATA\Google\AndroidStudio<version>.I’d like to confirm whether any user-installed plugins might also be stored in the
$dir\pluginsfolder. Additionally, should the contents of the$dir\modulesdirectory be persisted?
I tested it, and it seems that the plugins I installed are stored in AppData\Roaming\Google\AndroidStudio2024.3.2\plugins. I asked an AI, and it said that $dir/modules/ and $dir/plugins/ are folders created when Android Studio is installed, so they don't seem to need to be persisted.
I tested it, and it seems that the plugins I installed are stored in AppData\Roaming\Google\AndroidStudio2024.3.2\plugins. I asked an AI, and it said that $dir/modules/ and $dir/plugins/ are folders created when Android Studio is installed, so they don't seem to need to be persisted.
Thanks for your help. It seems removing the persist field from the manifest will resolve this issue. I'll submit a PR to fix it when I have a moment later.