CODEWITHSUNDEEP
xcodepermissionschmod
JimmyB
JimmyB

Reputation: 337

Cocoa application won't run because Contents/MacOS/Application is not a Unix Executable

My application runs fine on my system, and also on several others.

However, some people can't run the application because the file in /Contents/MacOS/ApplicationName is not a Unix executable file.

Inputting the following line in the terminal forces the application to be executable, and solves the problem:

chmod +x ApplicationName

Obviously this is a very hacky way around the problem, and I don't want to tell users to enter chmod to run my application. What am I doing wrong? Why is it appearing as a Unix executable file on some systems, but not others? It could be a permissions issue...

Upvotes: 1

Views: 386

Answers (1)

Thilo
Thilo

Reputation: 262494

at the moment, i transfer the app via dropbox to a client

Dropbox has problems with OS X metadata and permissions. Archive the application first (from the Finder context menu) and put the zip file into Dropbox.

Upvotes: 5

Related Questions