#7902 macOS Fedora Media Writer is damaged and can't be opened
Closed: Will Not/Can Not fix 2 years ago by smooge. Opened 2 years ago by chrismurphy.

When I go here:

And click on the Apple icon to the right of Fedora Media Writer, I get Fedora Media Writer 4.1.4 and it does not launch on macOS, instead I get an error message "is damaged and can't be opened."

Originally filed:

But I don't think it's a packaging problem, but a signing problem.

I ran sudo spctl --master-disable and the problem doesn't happen anymore. I can successfully image a USB stick. Of course, this isn't an acceptable work around for users, but I think it conclusively shows it's a signing issue of some sort.

@puiterwijk does the mac builds and would be able to look at this.

Metadata Update from @smooge:
- Issue assigned to puiterwijk
- Issue priority set to: Waiting on Assignee (was: Needs Review)

2 years ago

This turned out to be a known bug in Mac OS 10.13, with a documented workaround/fix at https://developer.apple.com/documentation/security/notarizing_your_app_before_distribution/resolving_common_notarization_issues#3087725 .
I intend to make a non-stapled build and distribute that when I get time to handle this.

Well, near as I can tell, Apple did kindof a craptastic thing with this bug by basically saying they're not going to fix it in 10.13 and users should just upgrade to 10.14. And now that 10.15 is out, and don't officially (i.e. they don't actually tell us one way or another) say what the support level is for n+2, I think it's reasonable to just dispense with this bug and any other bugs related to 10.13. (And I say that as a user who for like a two decades considered macOS my primary OS and now Fedora is my primary OS). Since Apple's way of "fixing" this bug is to say "upgrade" it's totally sane to tell our users the same thing, as crap as that is it's at least clarity, rather than ambiguity. shrug

Metadata Update from @smooge:
- Issue close_status updated to: Will Not/Can Not fix
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.