Unity builds for StandaloneOSX are not runnable.

When building for StandaloneOSX, the resultant file uploaded to artifacts isn’t runnable.

If you add executable permissions to the artifact the project can then be run.

chmod +x [PATH-TO-ARTIFACT]/StandaloneOSX/StandaloneOSX.app/Contents/MacOS/*

I’m not entirely sure where this would be added in the build pipeline, but I imagine these permissions should be added prior to artifact upload.

[davidmfinol]

It sounds like distributing a macOS app pretty much now requires going through the codesign process. I believe the initial issue (builds not runnable without chmod +x path/to/executable) has been fixed, so maybe we should close this issue and open a new issue for documentation about macOS distribution? We may want to create a docs/github/deployment/macos page that goes into codesign, notarization, and maybe even fastlane for mac apps.

[Zetonia]

None of the above worked for me however I did notice with the downloaded application that it has extra attributes when running

ls -la
drwxr-xr-x@ 3 <Zetonia>  staff    96 11 Mar 01:26 zetonia.app
	com.apple.quarantine	  57 

If i run the following command on the file then it opens fine.

xattr -d com.apple.quarantine zetonia.app