.ioc file generation

[sami_bahlous]

hello everyone , 

When I create a new project in STM32CubeIDE (version: 1.17.0), the .ioc configuration file is not generated in the project directory. Here’s what I’ve tried:

Project Type:

Created via File > New > STM32 Project (using the STM32 Project Wizard).

Selected my MCU/board .

Expected Behavior:

A .ioc file should appear in the project root after setup (enabling peripheral/clock configuration).

Actual Result:

Only standard project files (e.g., Core/, Drivers/, .project) are generated. No .ioc file exists.

I cannot open/configure the project in STM32CubeMX.

[AScha.3]

Hi,

seems to be "actual" problem, i had also;

Please try to

-Close STM32CubeIDE

-Delete all those files from your PC: .stm32cufinder, .stm32cubemx, .stm32cubeide and .stm32cube 

then restart the STM32CubeIDE and retest again.

If still strange problems, you could try :

 >>  To fix this, just remove this file inside your workspace:
 >>  .metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi
 >>  Hope this solves the issue.
 >>  (this file is the responsible of saving your workbench layout)

Then start IDE and see...and tell.

[sami_bahlous]

where can i find those files : .stm32cufinder, .stm32cubemx, .stm32cubeide and .stm32cube

[AScha.3]

oh...

on Linux : in your home directory,

on Win...first set file browser settings , to show "hidden" and system files, = all files;

also in your home directory,

on what system you are ?

[Andrew Neil]

There's a lot of it about today:

https://community.st.com/t5/stm32cubeide-mcus/ioc-file-not-generating/m-p/822500/highlight/true#M37461

[sami_bahlous · Accepted solution]

Thank you @AScha.3 for sharing this solution — it does help, but it's actually a temporary workaround.

When you delete the following files or folders:

• .stm32cubemx

• .stm32cubeide

• .stm32cufinder

• .metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi

STM32CubeIDE will:

• Rebuild its internal caches and indexes

• Reset corrupted UI/plugin states

• Stop referencing corrupted paths

This effectively gives you a clean environment, which is why the issue disappears temporarily. However, since the IDE may eventually rebuild the same corrupted state, this doesn't fix the root cause — it just resets the environment.

What actually worked for me:
Upgrading STM32CubeIDE from version 1.17.0 to 1.19.0 solved the issue permanently.

[Andrew Neil]

See the pinned post on this known issue:

STM32CubeIDE STM32Cube project creation issue