Can someone tell me what exactly do I need to do from this explanation?
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!