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!

  • 10
    You should definitely edit the executable flag of binaries in app bundles if they are not set. – Anthony Michael Cook Dec 26 '15 at 19:12
  • 1
    I'd add that I've specifically used this to fix applications created for OSX with Unity. My guess would be that these app bundles have been packaged up on another platform (like Windows) that doesn't get OSX permissions right. – Henry Cooke Aug 20 '16 at 20:38
  • 1
    I had to CHMOD 777 the file before it actually worked. Thanks. – Frank Barcenas Sep 30 '16 at 5:57
  • 1
    This happened to me when I downloaded an .app bundle from Dropbox via the web UI. – Dmitri Shuralyov Nov 24 '16 at 15:43
  • 3
    This can happen if you extract the app from a zip file using an unzip program other than the default Archive Utility.app. Sometimes unzipping with Archive Utility instead will preserve permissions and avoid the need for the solution here. – Jason Feb 11 '17 at 7:45

When I get The application SomeApp.app can’t be opened, I

  1. Open a terminal (/Applications/Utilities/Terminal.app),

  2. And type: sudo killall launchservicesd

  3. If the Dock is also misbvehaving, I'll also type killall Dock.

  4. Then, I am able to open SomeApp (or any app).

Is that ok with everyone?

  • 1
    Can you explain what this has to do with the question? – G-Man Dec 7 '15 at 5:41
  • When I get The application “SomeApp.app” can’t be opened', I kill launchservicesd, and sometimes Dock, and then I am able to open SomeApp. What is so bewildering about that? – mralexgray Dec 7 '15 at 5:46
  • 3
    @mralexgray: please expand your answer to include your comment and clarify your answer. Otherwise, this isn't much help, as-is. – studiohack Dec 8 '15 at 16:29
  • It's SO simple and SO clear. Run the command... and the problem is fixed. 'Nuff said. – mralexgray Dec 8 '15 at 17:00
  • 2
    Ran the commands. The problem wasn't fixed. Maybe if you put more information about what is actually happening when these commands are run it would help with fixing problem where this doesn't quite work as expected. It's simple, and clear enough, I suppose, but not complete. Notice there was no request to simplify or clarify this, but to expand it. The fact that it doesn't work for me right now makes me also wish it were expanded with more detail. – Todd Wilcox Apr 17 '16 at 22:13

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?

Not the answer you're looking for? Browse other questions tagged or ask your own question.