Thanks for looking at this.
Unfortunately has nothing to do with permissions, bug persists with correct permissions. Read the rest of the post for more thorough response.
Please note (for documentation / future support) that copying a file from a mapped windows drive within MacOS does *not* set correct permissions for the MacOS app. The correct way is to run "sudo chmod -R 0755 yourappname.app" or a helpful trick if working in a virtual machine is to zip the app and bring the zip over.. Dont ask me how zipping it works but it works.
Zipping the file and bringing it into OSX is the only way to correctly get it to run without having to mess with the permissions. Here are 3 tests:
drwxrwxrwx 3 nateschmold staff 102 3 Jul 19:05 test1.app
drwxr-xr-x 3 nateschmold staff 102 3 Jul 19:05 test2.app
drwxrwxrwx 3 nateschmold staff 102 3 Jul 19:05 test3.app
test1.app = bringing the over directly from Parallels into MacOS
test2.app = zipping in windows, transferring zip to macOS and unzipping in MacOS
test3.app = dragging the app from a mapped Windows drive into a folder within MacOS/finder.
test1.app and test3.app both result in "The application “testX” can’t be opened."
test2.app runs, but crashes with above error/bug.
I can confirm that zipping the file and bringing it over does indeed work with a file built with nwjs 0.20 -- app runs totally fine in that case.
To further confirm, if i set proper permissions on test1.app or test3.app using the terminal command:
sudo chmod -R 0755 test1.app
The app will finally stop giving the "The application __ can't be opened" window, and will instead run the app, but then crash with the error in the original post. So it doesn't have anything to do with permissions unfortunately, please try above steps to replicate the bug.