VSCode Extension not work well on last update on MacOS

[Sergey Golovin]

I set up nRF Connect SDK and VSCode Extension from scratch, but it looks like nRF Connect for VSCode does not work properly. When I start it from the side panel, dedicated areas from nRF Connect for VSCode start running thin p bar and never stop. I'm not able to open projects, samples etc. If I try to open an existing project by opening it's folder through the File menu of VSCode, the extension shows me the source, config files etc, I'm able to build a project, but the connection to RTT or UART is no working. Please, help me solve this issue. On the same config (using VSCode sync) on a Windows-running machine everything works well.

[Joakim Jakobsen]

Hi. 

I haven't seen any reports of major issues running VS Code on MacOS. 

Could you share some more information about OS version, how you installed, VS code version etc.?

You could also upload support information from the VS Code extension;

1. Open the command palette (Ctrl + Shift + P or View > Command Palette).
2. Write "nRF Connect: Generate support information" and press enter.
3. Copy the entire support information output.
4. Upload it here using Insert > Code or upload a .txt file with Insert > Image/video/file.

Br, 
Joakim

[Sergey Golovin]

Hi, sorry for the late reply.

MacOS 13.5.2, VSCode 1.82.2. I've installed it through Toolchain Manager.

I did what you suggested, but nothing happened. I saw on the Status bar (bottom of the VSCode window) a notification with a running circle and the text "Activating Extensions...". The same result is if select almost every option related to nRF Connect for VSCode extension. At the left panel on the nRF Connect for VSCode icon, there is a "clock" badge permanently. 

I tried to delete all VSCode and nRF Connect data and made a clean (as far as I can) installation of both of them without synchronization with my Windows station and with only the extension which the Toolchain Manager said was required for nRF Connect for VSCode.

I've tried to record a video, and on it, I tried to open an extension, then open an existing application, create a new application and finally generate support info as you asked.

[Joakim Jakobsen]

Thanks.

Don't know what the cause is, but I'll forward it internally. Maybe someone can give some insight to what can be done.

Br,
Joakim

[Joakim Jakobsen]

Hi.

Have you made any progress on this?

I got my hands on a mac and did some testing, but I'm not able to reproduce the issue. Asked around internally from people working with mac and they couldn't give me any pointers either.

Not sure what is causing this.

[Sergey Golovin]

Hi!

I gave up to solve this problem in a good way. I solved it radically, completely reinstall MacOS and install SDK on fresh new system. As far it is working good.

I blame my old MacOS installation with many of experiments with environments, packet managers and vanilla Zephyr. Hard to find out what exactly is root cause. 

In any case, thank you for support.

[Joakim Jakobsen]

Thanks for sharing the solution. And I'm happy you were able to make it work, although that was a bit troublesome solution.

Closing the ticket.

If you have any further questions, you are welcome to open a new ticket and we'll do our best to assist!

Br,
Joakim