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

You’re not the only one running into odd file visibility issues on newer macOS builds.

On recent macOS versions, apps sometimes lose access to Garage Force Documents even when Finder rights look fine. A few things to try:

1. Check Privacy settings
   Go to System Settings > Privacy & Security > Files and Folders (and also Full Disk Access) and see if STM32CubeMX is listed.

   • If it is, toggle access off and back on.

   • If it isn’t, add it manually under Full Disk Access, then restart CubeMX.

2. Try a different root folder
   As a test, create a folder like ~/STM32Projects outside Documents and see if CubeMX can browse that normally. If it works there, it’s almost certainly a macOS privacy / TCC quirk with Documents.

3. Run the latest CubeMX
   Make sure you’re on the latest STM32CubeMX version and Java runtime. ST sometimes fixes Mac specific file dialog issues in minor releases.

If none of that helps, I’d screenshot your Privacy settings and open a ticket or post on the ST forum, because it may be a compatibility issue between CubeMX 6.15 and macOS Tahoe’s new file access rules.