Multiline selection not visible after MacOS 26.2 update

[snigg]

It seems that after I updated MacOS to Tahoe 26.2 the IDE does not show selected text if over multiples lines correctly. This is a nightmare to work with, as it does not show selected text and can make you delete (overwrite) lines while editing.
Anyone else? Is there a setting to fix it?

[Ghofrane GSOURI]

Hello @snigg 

Thank you for posting.

A ticket has been escalated to dev team regarding this issue.

Internal ticket ID is 224479 and it will be fixed as soon as possible.

THX

Ghofrane

[snigg]

Any update on this? I have seen with the ticket ID this already has been raised last year. It is very annoying to use the IDE this way.

[Ghofrane GSOURI]

Hello @snigg 

Yes, I agree with you that this issue is very annoying. However, macOS 12.6.2 was published on December 12, 2025
(link: https://developer.apple.com/news/releases/?id=12122025c).

STM32CubeIDE 2.0.0 was released on November 18, 2025, and the ticket was escalated on 2025-12-30. We are doing our best to correct this behavior as soon as possible.

THX

Ghofrane

[snigg]

Its been more than a week and there is still no update. What is the timeline?!

[snigg]

ST, please take down the note you support MacOS and or set STM32CubeIDE to legacy status. You seemed to have invested in a Visual Code Studio integration of the STM32 stuff, so is this now the way to go? Could you at the very least be transparent in your strategy?!

[Arete]

Same issue here, please provide update.  Frustrating to say the least.

[Nick_Art]

It is really annoying - frustrating.

 

I also filed a ticket. Lets hope they will fix it. Or otherwise I'll buy other microcontroller from a different manufacturer.

VSCode does not have the nicer debug facility. 

[michbu1]

It is probably related to eclipse framework which had to adopt to some changes in macos. https://github.com/omnetpp/omnetpp/issues/1479. Maybe releasing new version based on newer eclipse fix the problem.

[callsignhermit]

For the record, this was finally fixed in the 2.2.0 update.