Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Webstorm not starting after installation due to "Cannot resolve resource bundle software.aws.toolkits.resources.MessagesBundle..." #4455

Open
alFReD-NSH opened this issue May 9, 2024 · 0 comments
Labels
bug We can reproduce the issue and confirmed it is a bug.

Comments

@alFReD-NSH
Copy link

alFReD-NSH commented May 9, 2024

Describe the bug
Webstorm is not starting after installing and stuck on splash screen. Getting a lot of different errors like the following:

Cannot resolve resource bundle software.aws.toolkits.resources.MessagesBundle for action XmlElement(name=action, attributes={class=software.aws.toolkits.jetbrains.core.explorer.devToolsTab.nodes.actions.CloneCawsRepository, id=aws.caws.devtools.actions.clone}, children=[XmlElement(name=add-to-group, attributes={group-id=aws.caws.devtools.actions.loggedin, anchor=first}, children=[], content=null)], content=null) [Plugin: aws.toolkit]

Check attached logs for more details.
webstorm_log.txt

Running Webstorm with disableNonBundledPlugins or deleting the plugin works.

To reproduce

  1. Install plugin version 3.1-241 on WebStorm 2024.1 RC
  2. Restart Webstorm

Expected behavior

  • Webstorm loads.

Your Environment

  • OS: Mac OS X
  • JetBrains product: Webstorm
  • JetBrains product version: WebStorm 2024.1 RC Build #WS-241.14494.180 , - AWS Toolkit version: AWS Toolkit version: 3.1-241
  • SAM CLI version: 1.107.0
  • JVM/Python version: JDK: 17.0.10; VM: OpenJDK 64-Bit Server VM; Vendor: JetBrains s.r.o. , Python 3.12.3
@alFReD-NSH alFReD-NSH added the bug We can reproduce the issue and confirmed it is a bug. label May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug We can reproduce the issue and confirmed it is a bug.
Projects
None yet
Development

No branches or pull requests

1 participant