Open bnest opened 2 years ago
We should add installation instructions with this workaround in the wiki.
I've added the workaround to the new installation instructions wiki page.
Re-open. Maybe we find a way to prevent this issue
this should be rather easy to fix: have travis set the +x attribute before uploading the file to aws, and when pushing a new release, set the required attribute on the file in a linux/mac environment before uploading the file?
This needs re-testing once the MacOS build using the unity-builder GitHub Action is working (see https://github.com/game-ci/unity-builder/issues/295 ) . Could be that they don't have this issue in the first place.
~Still happening on macOS Big Sur after adding +x
permission:~
OUTDATED check wiki instructions
Error opening release binary:
StandaloneOSX.zip
from https://github.com/UltraStar-Deluxe/Play/releases/download/v0.3.1/StandaloneOSX.zipchmod +x UltraStar Play.app
UltraStar Play.app
$ ls -l
total 0
drwxrwxr-x@ 3 gpalumbo 2049245171 96 3 May 2021 UltraStar Play.app
Issue type: Bug report
Actual behaviour
When downloaded the latest release https://github.com/UltraStar-Deluxe/Play/releases/tag/v0.3.1 and using the MacOS binary, it is not usable on MacOS 10.15.7 (19H524).
When double clicking it says: "UltraStar Play can't be opened". When using the terminal with "open UltraStar\ Play.app" it quits with error:
LSOpenURLsWithRole() failed with error -10810 for the file /Users/MyUser/Downloads/StandaloneOSX/UltraStar Play.app.
Expected behaviour
The binary should start US Play
Steps to reproduce
Should be the same on all MacOS Catalina installs
Details
The problem can be resolved / I resolved it.
This issue seems to be somehow related to the MacOS guard functionality for unknown binaries. Using:
Resolved the issue. Maybe including the executable permissions for macOS building process could already solve half the problem. Unsure how to prevent the attribute flag :-/