STM32N6570-DK - Problem opening projects from file system in CubeIDE

[SMoor.1]

I am trying to follow the steps from the community link below and I get an unusual messing

about "missing natures" (see paste below) when I try to open projects from file system.  I tried changing

my workspace location, but still get this message most of the time.  Other FAEs are seeing this issue as well. 

Any idea what causes this?  The suggestion solution is to install software that I have never heard about before. Any guidance would be appreciated. 

Thanks, Sonya

https://community.st.com/t5/stm32-mcus/how-to-debug-stm32n6-using-stm32cubeide/ta-p/800547

[Pavel A.]

What is your CubeIDE version? The linked article says 1.17.0 or newer is required.

Please don't install anything from the Eclipse marketplace to "fix" this issue, unless ST people advise so.

[SMoor.1]

I am using 1.18.1 version.  The files do not show up in project explorer once I encounter this message.  

Sonya

[SMoor.1]

I am able to build and run the project, but this error still comes up.  Please report this issue to the STM32CUBEide team as a fix is still needed in the latest release.  You can close the ticket now.

Sonya

[IBA1]

Yes, I encountered a similar issue. I had to update the IDE and repeatedly reinstall it to resolve the problem.

[IBA1]

May I know when the IDE is expected to reach a stable release? Your clarification would be greatly appreciated, ST.

[jhonwillaim21]

This looks like a tricky issue, especially since multiple users are seeing the same “missing natures” message. Sometimes CubeIDE fails to register the required project settings when importing directly from the file system, which can trigger errors like this. Since you referenced the STM32N6 debugging guide here (https://community.st.com/t5/stm32-mcus/click herehow-to-debug-stm32n6-using-stm32cubeide/ta-p/800547 ), it might be worth following the import steps mentioned in that document as well they can help ensure all project components and metadata are detected properly. Hopefully ST will address this inconsistency in a future update.