Descent3 icon indicating copy to clipboard operation
Descent3 copied to clipboard

[Runtime Issue]: Unable to run on MacOS ARM - “Descent3” is damaged and can’t be opened. You should move it to the Trash.

Open phubbard opened this issue 1 year ago • 2 comments

Build Version

v1.5.0

Operating System Environment

  • [ ] Microsoft Windows (32-bit)
  • [ ] Microsoft Windows (64-bit)
  • [X] Mac OS X
  • [ ] Linux (specify distribution and version below)

CPU Environment

  • [ ] x86 (32-bit Intel/AMD)
  • [ ] x86_64 (64-bit Intel/AMD)
  • [ ] ARM (32-bit)
  • [X] ARM64 (64-bit; sometimes called AArch64)
  • [ ] Other (RISC V, PPC...)

Game Modes Affected

  • [X] Single player
  • [ ] Anarchy
  • [ ] Hyper-Anarchy
  • [ ] Robo-Anarchy
  • [ ] Team Anarchy
  • [ ] Capture the Flag
  • [ ] Bounty
  • [ ] Entropy
  • [ ] Hoard
  • [ ] Monsterball
  • [ ] Cooperative

Game Environment

No response

Description

Setting the executable bit seems to break the binary signature, so the came can't run.

Regression Status

No response

Steps to Reproduce

Download the release Install as per instructions Set executable bit as per readme with chmod 755 Descent3.app/Contents/MacOS/Descent3 Try to run, either via terminal or Finder. Get “Descent3” is damaged and can’t be opened. You should move it to the Trash.

phubbard avatar Sep 01 '24 02:09 phubbard

Same issue as #540

tophyr avatar Sep 02 '24 07:09 tophyr

This will be fixed whenever #540 happens, but in the meantime, as a workaround, folks can apply ad-hoc codesigning to work around it. That's sufficient for ARM macOS versions to allow binaries to run and is, for example, what the Homebrew team is doing for binaries that they distribute.

So, in this case, running codesign --force --deep --preserve-metadata=entitlements,requirements,flags,runtime --sign - Descent3.app/Contents/MacOS/Descent3 should at least resolve running it from the terminal. I can't remember offhand whether the same also needs to be done to the bundle itself to run that, though I imagine that trying to do that would end up running into the same issue I did in #532.

Kreeblah avatar Sep 16 '24 06:09 Kreeblah

This is now fixed. You can grab the signed and notarized application from the latest build. Direct link as of this writing. You also don't need to manually set the executable bit anymore.

Eventually a new release will happen which will also be signed and notarized, but this will get you going in the meantime.

halprin avatar Feb 27 '25 23:02 halprin