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 a dialog saying "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.
Get path of the binary file of your app $your_app_binary_path. Give execution right to it.
chmod +x $your_app_binary_path
E.g.
chmod +x /System/Volumes/Data/Applications/:yourappname.app/Contents/MacOS/SecureTrustZone
You can get this path by a find command
sudo find / -name yourappname
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!
As in App Cannot Be Opened (even though that describes a workaround for the Gatekeeper app, it works for the scenario in the question as well)
When I get The application SomeApp.app can’t be opened, I
Open a terminal (/Applications/Utilities/Terminal.app),
And type: sudo killall launchservicesd
If the Dock is also misbvehaving, I'll also type killall Dock.
Then, I am able to open SomeApp (or any app).
Is that ok with everyone?
This can also happen when app is quarantined by macOS.
Ran into an interesting edge case where app sent over Telegram would not open.
Deleting app form “Applications” folder and downloading fresh copy fixed the issue.
