search

iljapostnovs / VSCodeUI5Plugin

Visual Studio Code Extension for UI5 Development
Apache License 2.0
61 stars 6 forks source link

Bug: Extension is not initializing in VSCode on macOs #411

Closed luizmz94 closed 3 months ago

luizmz94 commented 3 months ago

Describe the bug The SAPUI5 Extension for VS Code is not initializing on my macOS Intel machine. The notification "UI5Plugin: Initializing" keeps appearing, but the extension never fully starts.

To Reproduce Steps to reproduce the behavior:

  1. Install the SAPUI5 Extension from the Visual Studio Marketplace;
  2. Open Visual Studio Code;
  3. Wait for the extension to initialize;
  4. Observe the persistent notification "UI5Plugin: Initializing."

Expected behavior The extension should initialize properly and become ready for use, allowing me to utilize SAPUI5 development features.

Screenshots If applicable, add screenshots to help explain your problem. image

image

image

% CPU usage: image

Desktop (please complete the following information):

OS: macOS Intel

Additional context The issue occurs consistently every time I try to use the extension. I have tried reinstalling the extension and restarting VS Code, but the problem persists. My VS Code and macOS are both up to date.

I've already uninstalled and installed vs code, restarted the machine several times, but nothing made it work.

Project attachment If applicable, Project example for issue reproduction (You can add this if needed).

iljapostnovs commented 3 months ago

Hi,

Unfortunately, this description is not enough in order to reproduce the issue. According to this description, it should not work on all macOS, which is not true, which means, that it is either project specific, or machine specific issue. If it happens for one particular project, please provide minimal project example. If this behavior persists for all projects, I would say it is a machine issue. If it is a machine issue, I am not sure how I can help, because I can't reproduce it.

luizmz94 commented 3 months ago

I found the problem... When you mentioned that it could be something related to the project, I created another one, and it started working again.

In summary, I discovered that there was a .js file that was corrupted, with data in binary format. From what I analyzed, it was an .exe file, and someone changed the extension to .js, which caused the extension not to initialize and it was blocking all the other extensions.

In short, the problem was with me, sorry for the trouble, and thank you very much for the feedback.