Mac app "is damaged and cannot be opened"

[Deadlock7]

0.9.5 and 0.9.6 both have the same issue. I'm not technical enough to figure out why the app won't open.

[MCOfficer]

This was reported on discord as well, i probably should've filed an issue myself.

The upshot is that something in 0.9.5 (most likely dffc296, as the previous commit has been tested successfully by some mac users) broke something in the executable.

Unfortunately without a mac and no way of spinning up a VM, i'm kind of in the dark here. I guess I could revert to wgpu for mac only, but i've also been told that this is a signing issue - long story short, i have no clue and no way to test and need a technical person to help me out.

[tekdave1]

I am actually getting "You can’t open the application “ESLauncher2” because this application is not supported on this Mac." (intel MacBook Air 13-inch, Early 2015 , 2.2 GHz Dual-Core Intel Core i7 running Monterey (12.7.6 (21H1320))

V 0.9.4 was the last working version, something broke in 0.9.5

[charles-waite]

I'm not sure what exactly the issue is, I think it has something to do with Apple's new requirement for notarization of apps, but if you enter this command into the terminal xattr -rc /path/to/app/ESLauncher2.app the app will now open. I just tested this on the latest 0.9.7 release and prior to running this command it gave me the damaged app error listed above. After running the command the app launches and works fine. I'm using a MacBook Air M1 on Sequoia 15.5.

Might be a good idea to include this in the installation instructions for MacOS.

[Deadlock7]

Fantastic, thank you! I just did it on my MBP M1Max on Sonoma 14.7.2 and it works now. I wonder if doing this, then zipping and submitting the app release for download would make it work on another Mac.

[charles-waite]

I think this allow-lists the app locally with Gatekeeper so it's probably not possible to do this prior. Otherwise a malicious app could just do this and bypass MacOS security settings.