OSX 10.9 - application creshes at startup

[szwacz]

Hello,

This was reported to me by two different people using 10.9 Mavercks.
My app just don't want to start (open source so you can download just the same file: http://sputnik.szwacz.com/). I can't reproduce it on 10.8, so I decided to report it here.

App uses nw v0.8.0-rc1

Here is the full "stack trace":

open Sputnik.app
LSOpenURLsWithRole() failed with error -10810 for the file /Users/.../Downloads/Sputnik.app.

09.11.2013 17:37:40,436 Finder[188] CGSCopyDisplayUUID: Invalid display 0x0b40e935
09.11.2013 17:37:42,497 Finder[188] CGSCopyDisplayUUID: Invalid display 0x0b40e935
09.11.2013 17:37:44,538 com.apple.launchd.peruser.501[175]  (com.intel.nw.77824[76469]) Job failed to exec(3) for weird reason: 13
09.11.2013 17:37:44,545 Finder[188] 8837325: Attempting to SIGCONT to pid #76469 failed, with errno=#3, or the process failed to actually start
09.11.2013 17:37:44,557 Dock[185]   no information back from LS about running process LSASN:{hi=0x0;lo=0x528528}
09.11.2013 17:37:44,558 Finder[188] 8837325: Attempting to SIGCONT to pid #76469 failed, with errno=#3, or the process failed to actually start
09.11.2013 17:37:44,569 Finder[188] 8837325: Attempting to SIGCONT to pid #76469 failed, with errno=#3, or the process failed to actually start
09.11.2013 17:37:44,580 Finder[188] 8837325: Attempting to SIGCONT to pid #76469 failed, with errno=#3, or the process failed to actually start

..here is about 100 of these lines...

09.11.2013 17:37:44,580 Finder[188] 8837325: Attempting to SIGCONT to pid #76469 failed, with errno=#3, or the process failed to actually start
09.11.2013 17:37:44,580 Finder[188] 8837325: Attempting to SIGCONT to pid #76469 failed, with errno=#3, or the process failed to actually start

[jsoverson]

I'm able to start this and other node-webkit apps on osx 10.9

[szwacz]

Ok, so I belive it is not my app fault :)
If someone have idea for a test what's going on, I can ask those people if they can run it on their machines.

[szwacz]

Third person just reported to me this issue. Really only my users have this problem? :)

[szwacz]

Problem solved. It is not node-webkit fault.
My app is distributed in zip file, and some non-standard archivers while unzipping don't give execution privilige to any file inside the package. So all files inside myApp.app/Contents/Frameworks have no right to execute and OSX is printing out so nothing-telling message.

This behaviour is universal to all versions of OSX, not only Mavericks.