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

[TDK]

Tahoe isn't listed as a supported OS. Might have to wait.

With the shift to VS Code, it's not clear how long it will take to support newer OS versions.

[SloBlo]

I don't agree that is cutting it. Other user folders, such as Music, the dialog is enumerating just fine, and it has got identical rights settings. There must be something else going on.

In addition, the issue doesn't seem to appear widespread in the forum. I deem that would be different if there is a general core issue using CubeMX on Tahoe.

[Ghofrane GSOURI]

Hello @SloBlo 

As mentioned by @TDK Mac Tahoe 26.1 is not listed as a supported operating system for STM32CubeMX 6.15.0. This means that the application has  not been tested or optimized for compatibility with this version of macOS. As a result, certain features such as file system access may not function as expected.

THX

Ghofrane

[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

[Ghofrane GSOURI]

Hello ​@william_Lucas98 

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.

 

[Jackson_512]

Thanks for sharing this.
Since CubeMX can read sibling folders but not the Documents folder, it does sound more like a macOS Tahoe compatibility or sandboxing issue than a standard permission problem. Did the accepted workaround continue working after restarting CubeMX or the Mac?
It would also be helpful to know whether the same issue appears in STM32CubeIDE.