STM32CubeIDE 1.19.0 creates "Empty" project from valid .ioc file

[Olitronik_Lab]

I’m using STM32CubeIDE v1.19.0 (Build: 25607_20250703_0907) on Linux, and I’ve run into a recurring issue when creating a project from an existing .ioc file.

When I go to:
File > New > STM32 Project from existing .ioc
and select a valid .ioc file (that opens correctly in STM32CubeMX and works on real hardware), the “Targeted Project Type” field changes automatically from STM32Cube to “Empty”, and the resulting project has no .ioc linked and no code generated.

This issue happens even with:
- Fresh .ioc files
- Clean, empty directories
- New workspaces
- Verified CubeIDE 1.19 installation

However, if I open the same .ioc in **STM32CubeMX (standalone)**, perform a **Save As**, and generate the code with toolchain set to `STM32CubeIDE`, then import the project manually into CubeIDE — everything works fine.

This same issue had occurred in CubeIDE 1.18.x and seems to persist in 1.19.0.

Importantly, this workflow **used to work fine**, and suddenly stopped working **without any visible or intentional change** on my side. It’s as if the IDE stopped recognizing the .ioc structure properly, even though the files are valid.

It appears that the automated project creation wizard fails to recognize valid .ioc files unless they've been freshly saved/generated via CubeMX. Possibly an issue with metadata detection.

Can this be confirmed as a bug? Are there any plans to fix this behavior?

Thanks in advance!

[Andrew Neil]

See the pinned post on this known issue:

STM32CubeIDE STM32Cube project creation issue

[Olitronik_Lab]

Thank you for the suggested workaround. I’ve followed all the steps:

• Disabled auto-refresh in both STM32CubeIDE and STM32CubeMX

• Deleted the .stmcuFinder folder

• Restarted STM32CubeIDE

Unfortunately, the issue still persists — the "Targeted Project Type" field remains set to "Empty" when importing a valid .ioc file.

I can continue working by manually generating the project using STM32CubeMX and importing it into CubeIDE, but I hope a permanent fix will be included in a future update.

Thanks again for your support.

[Andrew Neil]

---

@Olitronik_Lab wrote:

I hope a permanent fix will be included in a future update.

---

As the pinned post shows, ST are working on it ...

[Ghofrane GSOURI]

Hello @Olitronik_Lab 

After performing the instructions mentioned in this post , please make sure to use a  new workspace.

THX

Ghofrane

[Olitronik_Lab]

Thank you for the reply.

Instead of creating a brand new workspace, I removed the `.metadata` folder from my current one (effectively resetting it), as this usually resolves similar issues.

After also following the suggested steps (disabling auto-refresh, deleting `.stmcuFinder`, etc.), the issue still persists — the “STM32Cube” project type is not recognized when importing a valid `.ioc`.

I’ll keep using the manual workaround via STM32CubeMX and will monitor for updates.

Thanks again for the assistance.

[nit4tin]

Same issue here, tried uninstalling and reinstalling the application too. 

Deleted the .meta folder, issue still exist

Created new workspace, issue still exist

Downloaded and installed a fresh installation, issue still exist.

Kindly let me know, if you find a fix for this Bug.

[Ghofrane GSOURI]

Hello @nit4tin 

Have you followed the instructions mentioned in this post ?

THX

Ghofrane