Warning: macOS update to 26.1 breaks Eclipse text selection

[st_otto]

Hello,

if you are using macOS and STM32CubeIDE and need it productively you should currently refrain updating your macOS. Due to a bug in Eclipse (https://github.com/eclipse-platform/eclipse.platform.swt/issues/2621) text selection does no more work via dragging your mouse or using shift+arrows.

There is already a fix but STM32CubeIDE does not provide the fix as update as of now.

I already filed a case. 

[Ghofrane GSOURI]

Hello @st_otto 

I'm currently checking this .I will get back to you as soon as possible

THX

Ghofrane

[st_otto]

Thanks @Ghofrane GSOURI 

If you need it, this is the case no. I created: 00247560

[Ghofrane GSOURI]

Hello @st_otto 

In the meantime, STM32CubeIDE 1.19.0 is not supported on macOS 26.1, according to release note RN0114.

 

 

 

[Andrei Chichak]

Yeah, this is fixed in Eclipse 2025-12.

It's just a matter of time for ST to make their changes and updates, do regression testing, and send it out.

APPLE!!!!

[jolyon]

Same for me. Any update or workaround at all?

 

Thanks.

[grisom13]

looking on update on this

[ahmetdogan]

This issue still not resolved even on v2.0.0..How can ST not resolve such a critical issue for months?

[grisom13]

To Be fare its not ST, its so called Eclipse part of the ST software. But indeed, a lot of frustrations.

[ahmetdogan]

Just realized that even cmd+c & cmd+v (copy/paste) is not working as well..

[ahmetdogan]

Well.. They should have done their work of integrating the new Eclipse which includes the fix.. I should not have wasted half a day...

Here is a work around that works on STM32CubeIDE v1.19.0.

SWT files inside STM32CubeIDE need to be updated. Do it at your own risk.. Backup your app and files in advance..

 

Download this file:

https://archive.eclipse.org/eclipse/downloads/drops4/R-4.38-202512010920/download.php?dropFile=repository-4.38.zip

Inside the zip look for two SWT files under plugins folder:

org.eclipse.swt_3.132.0.v20251124-0642.jar

org.eclipse.swt.cocoa.macosx.x86_64_3.132.0.v20251124-0642.jar

Open your Applications folder, right click on STM32CubeIDE app and click on show package contents..

Go to Contents/Eclipse/plugins folder..

replace these two files with the ones you have extracted from the new Repository 

org.eclipse.swt_3.127.0.v20240903-0618.jar

org.eclipse.swt.cocoa.macosx.x86_64_3.127.0.v20240903-0618.jar

 

Update the bundles.info File

This file is the "source of truth" for the IDE. We need to update it to point to the new files.

Navigate to: /Applications/STM32CubeIDE.app/Contents/Eclipse/configuration/org.eclipse.equinox.simpleconfigurator/

Open the file bundles.info with a text editor (like TextEdit).

Search for the line starting with org.eclipse.swt,. It will look something like this: 

org.eclipse.swt,3.127.0.v20240903-0618,plugins/org.eclipse.swt_3.127.0.v20240903-0618.jar,4,false

Edit that line to match your new version and filename exactly: 

org.eclipse.swt,3.132.0.v20251124-0642,plugins/org.eclipse.swt_3.132.0.v20251124-0642.jar,4,false

Search for the line starting with org.eclipse.swt.cocoa.macosx.x86_64

Edit that line as well: 

org.eclipse.swt.cocoa.macosx.x86_64,3.132.0.v202511240642,plugins/org.eclipse.swt.cocoa.macosx.x86_64_3.132.0.v20251124-0642.jar,4,false

Save and close the file.

 

Remove macOS Quarantine

macOS often blocks JAR files downloaded from the internet. Run this in Terminal to ensure the IDE can "see" them:

xattr -d com.apple.quarantine "/Applications/STM32CubeIDE.app/Contents/Eclipse/plugins/org.eclipse.swt"*

Delete the folder: /Applications/STM32CubeIDE v1.19.0.app/Contents/Eclipse/configuration/org.eclipse.osgi/

Delete the SWT cache: rm -rf ~/.swt (in Terminal).

Launch with the -clean Flag

Open Terminal and launch the IDE with the clean flag to force the plugin registry to rebuild:

"/Applications/STM32CubeIDE.app/Contents/MacOS/stm32cubeide" -clean

[jolyon]

I agree. I really like ST's products, and have done for years back to the ST20, but I think they really need to work harder to keep their tools current and up-to-date (don't get me started on the BLE mess).

I am on V2.0.0 now and I was hoping it would be fixed given that this is a major version increment, but alas no.

Thank you so much for taking the time to offer the work-around, I am wondering if I should downgrade to apply, or wait a few days longer....

My gut feeling is that everyone is being pushed over to VS Code and CMake which is perhaps why these types of bugs are left for so long.

On a side note, and since I am moaning, the bug where it messes up the path to the linker file on code regeneration is back. It preserves a custom filename, but trashes the path again. Not sure how you fix a bug one day and then put it back in...

Jo

 

 

[ahmetdogan]

Just tested this work around for v2.0.0.. It works on it too..

[jolyon]

Great. Thanks