Skip to main content
VBiri.1369
Associate
November 18, 2019
Solved

“STM32CubeIDE�? is damaged and can’t be opened

  • November 18, 2019
  • 18 replies
  • 6665 views

Hi!

I am trying to install the IDE on my macOS 10.13 (High Sierra), after completing the installation when trying to open it it gives the message: ' “STM32CubeIDE�? is damaged and can’t be opened. You should move it to the Trash. '

I tried to re-download it and re-install it several times, after deleting the previous copies, but after many attempts I get the same problem. I even tried installing the previous version but it said it was incompatible.

Any suggestions? Thanks in advance!

This topic has been closed for replies.
Best answer by Julien D

Answer, at least workaround, has already been shared in another topic https://community.st.com/s/question/0D50X0000BUh6nK/not-able-to-open-stm32cubeide-110-on-macos-mohave-10146?s1oid=00Db0000000YtG6&t=1574078933520

Try the following command in a Terminal:

xattr -c /Application/STM32CubeIDE.app

The dev team works on a more sustainable fix.

18 replies

Julien D
Julien DBest answer
ST Employee
November 18, 2019

Answer, at least workaround, has already been shared in another topic https://community.st.com/s/question/0D50X0000BUh6nK/not-able-to-open-stm32cubeide-110-on-macos-mohave-10146?s1oid=00Db0000000YtG6&t=1574078933520

Try the following command in a Terminal:

xattr -c /Application/STM32CubeIDE.app

The dev team works on a more sustainable fix.

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
VBiri.1369
Associate
November 18, 2019

Thanks! That worked!

Only a small typo in the path, missing the s from Applications, so I believe the following command is the one that should be used:

xattr -c /Applications/STM32CubeIDE.app

Cartu38 OpenDev
Graduate II
January 10, 2020

.

PTore.1
Visitor II
February 2, 2020

FYI bug is still there, I'm seeing this attribute (x'd out a few hexdigits):

% xattr -l /Applications/STM32CubeIDE.app
com.apple.quarantine: 0181;5e3710ee;Firefox;E5x9x0Fx-94x7-4Cx4-98BF-58FCEx72x780

PTore.1
Visitor II
February 2, 2020

Also, it would be super cool if the installer had a checkbox option to manage a config in /etc/paths.d/ for CLI support.

Chet Ferry
Associate II
April 7, 2020

Any plans to fix this???

0xD
Associate
May 29, 2020

This bug is still there.

Please allow me to say, as a new STM32 user that has so far been impressed by your hardware and good reputation, trying to get started with your software on mac os is an utter nightmare, and has shattered the image you have built with your hardware to pieces. It take ridiculous effort to get any of your software running on mac os. Plus when it runs I feel like I am using 10+ years old software. Its ok to make mistakes (and fix them), but: this > mistake. And to make matters worse its not fixed, this specifically not in 6+ months. Wow ST!

We are having 2020. you can't expect your users to run a bunch of terminal commands to get essential software of a major manufacturer running on a modern operating system just to be presented by a ui from the early 2000s. :folded_hands:

Nello
Associate II
May 15, 2022

2 years later, this bug is still there. Pathetic.

JHoun.1
Associate III
June 11, 2020

Disappointingly still not working. The workaround isnt working properly for me either - am unable to upload to boards / start debugger properly still on OSX.

If its not fit for purpose, it needs to be pulled and people just rely on the windows version and run a virtual machine.

cm0x4d
Associate
September 29, 2020

Version 1.4 is totally ****** up on a MacOS when installed on a case sensitive file system.

By the way, almost all other tools from ST do not work either on a case sensitive filesystem on a Mac.

This is just embarrassing!

Chet Ferry
Associate II
December 10, 2020

So.... Any plans to fix this? Version 1.5 on MacOs Catalina still requires doing the command line thing as pointed out by Julien D.