-
Notifications
You must be signed in to change notification settings - Fork 37
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
App reported as damaged and won't run #595
Comments
Perhap quarantined a la https://www.reddit.com/r/macsysadmin/comments/13vu7f3/app_is_damaged_and_cant_be_opened_error_on_ventura/
Related, we might need to sign the app (see #183 and #530) Aside: worked on getting Apple Dev creds for my org but the reset is sent to a Mac not in my immediate possession (i.e., not the MBP M3), so will need to circle back. That auth might only permit iOS development, so perhaps it's moot. See also: ianmartinez/AsciiStudio#2 (comment)
|
https://eclecticlight.co/2017/08/15/quarantined-more-about-the-quarantine-extended-attribute/ explains the role of the quarantine attribute. via https://github.com/orgs/Homebrew/discussions/4302
|
See https://gist.github.com/bpteague/750906b9a02094e7389427d308ba1002 for February 2025 instructions on signing. |
https://github.com/orgs/Homebrew/discussions/3348 describes the ``--no-quarantine'' flag that can be used so that macOS does not report the app as "damaged". |
Consistent between homebrew and DMG'd .App installation. 594 has the trace on some intermittent issue with homebrew. WAIL 0.2025.03.03. Apple M3.
The text was updated successfully, but these errors were encountered: