Recent changes to 4: App won't launch on macOS 11 because of code signing issues

#4 App won't launch on macOS 11 because of code signing issues

Daniel Aarno — Sun, 17 Nov 2024 14:54:10 -0000

Actually, it seems to just be a quarantine issue.
I managed to run the app just by having executed:

xattr -d com.apple.quarantine /Applications/MacCrackAttack.app.

And Thanks, @macbishop for having crafted and released this mac version.

#4 App won't launch on macOS 11 because of code signing issues

Daniel Aarno — Sun, 24 Oct 2021 10:06:06 -0000

I think there is some other issue involved as only HFS+ filesystems were involved when building. I no longer own a Mac (Intel or ARM), so if anyone is up for cutting a new release, I'd be more than happy to have it uploaded here.

#4 App won't launch on macOS 11 because of code signing issues

Erik Larsson — Sat, 23 Oct 2021 05:16:35 -0000

The solution may be to use an APFS or HFS+ filesystem when signing the app. Then the '._'-files won't be included in the code signing manifest.

App won't launch on macOS 11 because of code signing issues

Erik Larsson — Sat, 23 Oct 2021 05:12:24 -0000

When attempting to launch the ARM/x86_64 version of the app (MacCrackAttack_v1.1.6.dmg) macOS complains and says the app is damaged. Looking more closely with codesign I found the following issue:

$ codesign -v -v -v /Volumes/MacCrackAttack_v1.1.6/MacCrackAttack.app/
/Volumes/MacCrackAttack_v1.1.6/MacCrackAttack.app/: a sealed resource is missing or invalid
file missing: /Volumes/MacCrackAttack_v1.1.6/MacCrackAttack.app/Contents/Resources/data/._logo.tga
file missing: /Volumes/MacCrackAttack_v1.1.6/MacCrackAttack.app/Contents/Resources/data/._.DS_Store
file missing: /Volumes/MacCrackAttack_v1.1.6/MacCrackAttack.app/Contents/Resources/data/._splash.tga
file missing: /Volumes/MacCrackAttack_v1.1.6/MacCrackAttack.app/Contents/Resources/data/._logo_x.tga

So some files that were present when signing are not present in the final product. It looks like these are AppleDouble files hinting that the app may have resided on a FAT/exFAT filesystem when signing it, as those files are used to store extended attributes on filesystems that don't support them natively.