OpenJK icon indicating copy to clipboard operation
OpenJK copied to clipboard

All MacOS Arm Files are damaged for Current Release

Open davidagnome opened this issue 1 month ago • 1 comments

https://github.com/JACoders/OpenJK/commit/d1cb662f07dfa4c1999edfb5c1a86fd1c6285372

These files are all damaged. There's no security prompt or anything. Just "this application is damaged notices" OpenJK-macos-arm64.tar.gz OpenJO-macos-arm64.tar.gz

The builds linked from Mac Source Ports do run however: https://github.com/MacSourcePorts/MSPBuildSystem/releases/download/OpenJK_2025-07-12/OpenJO-SP-1.0.dmg https://github.com/MacSourcePorts/MSPBuildSystem/releases/download/OpenJK_2025-07-12/OpenJK-MP-1.0.dmg https://github.com/MacSourcePorts/MSPBuildSystem/releases/download/OpenJK_2025-07-12/OpenJK-SP-1.0.dmg

davidagnome avatar Nov 20 '25 02:11 davidagnome

This is because macsourceports pays for an apple developer license, if you follow the install guide on jkhub, you can run the openjk builds. It's just a terminal command to fix this.

taysta avatar Nov 22 '25 05:11 taysta

There might be a bigger issue here. I ran the xattr command to get rid of the "damaged" error, but it crashes like so:

Crashed Thread:        0

Exception Type:        EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid))
Exception Codes:       UNKNOWN_0x32 at 0x00000001056a8000
Exception Codes:       0x0000000000000032, 0x00000001056a8000

Termination Reason:    Namespace CODESIGNING, Code 2 Invalid Page

ArtisIan97 avatar Dec 12 '25 12:12 ArtisIan97

There might be a bigger issue here. I ran the xattr command to get rid of the "damaged" error, but it crashes like so:

Crashed Thread:        0

Exception Type:        EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid))
Exception Codes:       UNKNOWN_0x32 at 0x00000001056a8000
Exception Codes:       0x0000000000000032, 0x00000001056a8000

Termination Reason:    Namespace CODESIGNING, Code 2 Invalid Page

Did you also codesign

taysta avatar Dec 13 '25 04:12 taysta

I tried before, but I just realized that I was doing the procedure wrong. Tried again today and got it working.

At the same time, I think this should be mentioned in the installation notes to help others who don't know how to fix it. Otherwise, they're going to think the whole project is broken.

ArtisIan97 avatar Dec 13 '25 07:12 ArtisIan97