stm32CubeMX not listing Documents contents on Mac Tahoe

[SloBlo]

I recently switched to Mac Tahoe 26.1 and it seems since then stm32CubeMX 6.15 is not listing the contents of my Documents folder anymore. It doesn't seem like a rights management issue since

• there were no changes to the Documents rights
• they are identical to sibling folders which CubeMX would properly enumerate

And yes, the folder does have contents and is not empty as shown in the screenshot from the file open dialog attached.

Anyone experiencing similar issues? How to come around that?

Best,

Oliver

[Ghofrane GSOURI]

Hello @SloBlo 

Thank you for your valuable contribution.

Issue has been escalated to dev team under internal ticket ID 222404 .

I will keep you posted with updates.

THX

Ghofrane

[Ghofrane GSOURI]

Hello @SloBlo 

For macOS the full disk access is required to load project files or install other packages from the file system. To enable full disk access for STM32CubeMX:
1. Go to “System preferences” and click to open “Security & Privacy” window
2. Select “Privacy” tab
3. Select “Full Disk Access” from the left panel
4. Click the checkbox to enable full disk access to STM32CubeMX

--> Hence, all folders will be visible.

This is detailed in the user manual of MX, particularly in section "3.1.1. Supported operating systems and architectures" (see attached screenshot from MX UM)...

[SloBlo]

Dear Ghofrane,

thank you for following up on this. Following your suggestion I can confirm that CubeMX can access Documents folder and I am able to continue working on projects in my preferred location on MacOS Tahoe.

2 remarks, though, to STM and anyone facing similar situation:

• STM CubeMX installer did not create an entry within the Privacy & Security section nor ask for Full Disk Access during installation (as many other applications do since Tahoe). With this in place nothing of the above would happen and keep a lot of frustration from STM customers
• I had to add the CubeMX application manually now (using '+' button on the Full Disk Access page below). That is your workaround in the meanwhile :)

Regards,

Oliver