Mac Silicon build 2.6.0 is ’damaged‘, code signing issue?

• Sv 9 0

  Message from Sven on …
  Hi,
  I downloaded the macOS Silicon version 2.6.0, and my Mac says it cannot start the application because it is ”damaged” (Tahoe 26.4.1). After applying the terminal command to forcibly remove the app from quarantine (xattr -rd com.apple.quarantine {app path}) the app crashes at start.
  The Intel build seems to start properly, after allowing macOS to open it (in System settings).
  What can we do to make the Silicon build work?
  
  From crash details:
  
  Exception Type:    EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid))
  Exception Subtype: UNKNOWN_0x32 at 0x0000000104ab8000
  Exception Codes:  0x0000000000000032, 0x0000000104ab8000
  
  Termination Reason:  Namespace CODESIGNING, Code 2, Invalid Page
  
  Note: the disk image is labeled ”../macos/Polyphone” which doesn’t instill confidence because paths should be avoided here. It also means the image is in a dot-directory in /Volumes. As such, it has the side effect that the volume is not displayed on the desktop. Suggest to just label it ”Polyphone”.

Sign in or register to take part in discussions.