Skip to content

make StandaloneOSX app runnable #99

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 13, 2020
Merged

make StandaloneOSX app runnable #99

merged 3 commits into from
Jun 13, 2020

Conversation

nathanleiby
Copy link
Contributor

@nathanleiby nathanleiby commented Jun 11, 2020

Potential fix for: #77

Questions:

  • The contributor guidelines request adding tests, but given that this happens in the shell script I wasn't certain if/how to do that best. Any suggestions, or is a manual verification good enough?
  • In the issue it discusses fixing Linux builds as well, but I haven't yet tested if they're broken or determined the path where the executable would need to be updated. Do we want to include that here as well or just Mac?

@codecov
Copy link

codecov bot commented Jun 11, 2020

Codecov Report

Merging #99 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #99   +/-   ##
=======================================
  Coverage   94.67%   94.67%           
=======================================
  Files          14       14           
  Lines         244      244           
  Branches       48       48           
=======================================
  Hits          231      231           
  Misses         13       13           

@nathanleiby
Copy link
Contributor Author

After adding logging, I now see that it ran here (https://github.com/webbertakken/unity-builder/runs/760264818):

Making the following path executable: /github/workspace/build/StandaloneOSX/StandaloneOSX.app/Contents/MacOS/*

Copy link
Member

@webbertakken webbertakken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

The contributor guidelines request adding tests, but given that this happens in the shell script I wasn't certain if/how to do that best. Any suggestions, or is a manual verification good enough?

Feel free to leave the tests for the bash part away.

In the issue it discusses fixing Linux builds as well, but I haven't yet tested if they're broken or determined the path where the executable would need to be updated. Do we want to include that here as well or just Mac?

I think it's OK to do the Linux part in a different PR as it's important to test these changes, since many people are using this.

@webbertakken webbertakken merged commit 229b0d0 into game-ci:master Jun 13, 2020
nathanleiby added a commit to CleverGameDev/Cleverfall that referenced this pull request Jun 13, 2020
@nathanleiby
Copy link
Contributor Author

nathanleiby commented Jun 13, 2020

I recently pushed a commit to use the latest version of this github action (CleverGameDev/Cleverfall@5279802) and verified that the output is now executable (https://clevergamedev.itch.io/cleverfall).

NOTE: You still have do a security override to allow running a binary from unverified developer, but after that it works as expected vs hitting a 2nd error. This was expected; it's just standard MacOS security.

Thanks for shepherding this out! 🐑

@mastef
Copy link
Contributor

mastef commented Oct 6, 2020

@nathanleiby @webbertakken so I recently tried the MacOS build, and the resulting StandaloneOSX.app and the StandaloneOSX.app/Contents/MacOS/ProgramName were not executable. So double-clicking on the StandaloneOSX.app would come up with an error :
image

Trying to run it through terminal, would throw this error :

$ open StandaloneOSX.app/
LSOpenURLsWithRole() failed with error -10810 for the file /Downloads/Build/StandaloneOSX/StandaloneOSX.app.

After running chmod +x on both of them, I was able to open the app.

Maybe a regression is happening? Or the chmod +x is getting lost in the .zip?

@webbertakken
Copy link
Member

@mastef thank you for reporting your issue.

Could you please open a new issue for this that is not closed and copy paste all information you've just provided?

That way also other contributors may be able to help.

@mastef
Copy link
Contributor

mastef commented Oct 9, 2020

@webbertakken I think re-opening #77 might be the better approach - as it seems to be a regression

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants