Problem: after downloading an application in OS X Yosemite (10.10.x) trying to open the application (either from the command-line or by double-clicking the application) produces an "The application “SomeApp.app” can’t be opened." Note that this differs from the "SomeApp can't be opened because it was not downloaded from the Mac App Store" or "SomeApp can’t be opened because it is from an unidentified developer” message that is the result of Gatekeeper settings.
After extensive trial-and-error, and a lot of fruitless Googling, I found the solution required modifying the executable status of the "inner" application file. This line:
chmod +x SomeApp.app/Contents/MacOS/*
Fixed the problem in all cases that I observed. The
+x flags a file as executable, and the only file in the
/Contents/MacOS/ directory is a binary representing the actual file that should be executed when you double-click the application (a
.app file is really just a folder).
Hope this helps someone else!
When I get The application
SomeApp.app can’t be opened, I
Open a terminal (
sudo killall launchservicesd
If the Dock is also misbvehaving, I'll also type
Then, I am able to open
SomeApp(or any app).
Is that ok with everyone?
protected by Community♦ Aug 14 '15 at 18:41
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?