Skip to content
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

macOS Build not Opening #85

Closed
dejl opened this issue Feb 2, 2024 · 9 comments
Closed

macOS Build not Opening #85

dejl opened this issue Feb 2, 2024 · 9 comments
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@dejl
Copy link

dejl commented Feb 2, 2024

Hi

I have latest macOS Sonoma 14.3 (Apple M1)
The macOS build doesn't open. I have also tried the CLionly build, same message
Screenshot 2024-02-02 at 6 07 55 pm

I have also tried launching the executable in the macOS folder of the .app, and the same message.

@albertogarciacz
Copy link

albertogarciacz commented Feb 6, 2024

I have the same problem. Running on Sonoma 14.3 (M2 MAX).

@vicmarto
Copy link

Same here (Sonoma 14.3 on an INTEL mac).

@speed47
Copy link
Owner

speed47 commented Feb 17, 2024

Hello,

Unfortunately I don't have a Mac, so I'm pretty blind about the MacOS build. The only thing I have is the automated regression tests on GitHub (which do pass successfully, so the binary does work correctly there), and I also use GitHub actions to build the Mac version and package it.

I suspect this might be an issue with the dmg packaging, as the binary does work in the regression tests launched by GitHub on a Mac, using macOS 12. Could one of you unpack the dmg file and try to launch the binary manually?

I see that GitHub now supports macOS 13 and 14 in beta, so I could also try to build under those, but I suspect/hope that an app built for macOS 12 is also supposed to work on a more recent version?

@speed47 speed47 added bug Something isn't working help wanted Extra attention is needed labels Feb 17, 2024
@albertogarciacz
Copy link

albertogarciacz commented Feb 19, 2024

I mounted the dmg and then ran /Volumes/dvdisaster-v0.79.10-pl2-cli-only/dvdisaster.app/Contents/MacOS/dvdisaster from the command line. Unfortunately resulting in the same error message.

@dejl
Copy link
Author

dejl commented Feb 22, 2024

The latest release is the same as above as well

I cloned the repo and can get a working build from source without any fuss, though.

Screenshot 2024-02-22 at 11 40 39 pm

@vwellum
Copy link

vwellum commented Mar 11, 2024

When sht like this happens:
sudo xattr -cr /Applications/dvdisaster.app
usually fixes most of the things.

@speed47
Copy link
Owner

speed47 commented Mar 11, 2024

When sht like this happens: sudo xattr -cr /Applications/dvdisaster.app usually fixes most of the things.

Oh, is that because macOS tags the file as being downloaded from Internet and somehow insecure, or something like that?
If this fixes the problem, can somebody run xattr -lr /Applications/dvdisaster.app before, so that I can get an idea of which extended attributes are causing this behavior?

@albertogarciacz
Copy link

albertogarciacz commented Mar 11, 2024

I've just run sudo xattr -c /Applications/dvdisaster.app and then the app and it seems to solve the problem described.
Screenshot 2024-03-11 at 17 04 11
Please find output of sudo xattr -l /Applications/dvdisaster.app that I had ran beforehand.

com.apple.provenance:
0000   01 00 00 71 6A 30 22 ED C8 C3 53                   ...qj0"...S

com.apple.quarantine: 0183;65ef2a9f;Safari;1E4929C3-C9A7-461B-BE3F-4E5D8CB1E8FF

@speed47
Copy link
Owner

speed47 commented Mar 30, 2024

Thanks a lot for the feedback. A lot of resources can be found online about this com.apple.quarantine attribute behavior, which seems to be set when a program is downloaded from anywhere except the Apple store. The error message is extremely misleading, I have no idea why they didn't go the "warning: this program has been downloaded from an unknown source, please run it only if you completely trust the source" instead, but, well, that's how it is.

I've added the information on the release page and referenced this issue. Thanks!

@speed47 speed47 closed this as completed Mar 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

5 participants