CHIRP

The macOS builds of CHIRP ship with an invalid code signature that causes the app to crash with "EXC_CRASH (SIGKILL (Code Signature Invalid))" when run. This appears to have been the cause of numerous bug reports and even has a section in the wiki devoted to it. Unfortunately the wiki provides and erroneous explanation and an unreasonably complicated partial solution. The wiki claims that the problem stems from CHIRP being unsigned. This is not true: CHIRP is signed, but the signature is invalid, the exception message macOS makes this clear. The wiki suggests signing the application with a local dev certificate, but this is unnecessary as macOS, even the bleeding edge Monterey will happily run unsigned applications provided the user gives consent. Simply removing the invalid signature from the binary solves the issue codesign --remove-signature /Applications/CHIRP.app/Contents/CHIRP

The macOS user experience would be much better if you simply stopped signing releases with whatever broken cert you have in your build system. macOS is not iOS and applications do not need to be signed to run. Right clicking and choosing "Open" once to bypass the unsigned app soft-block (more info on the actual process here: https://support.apple.com/guide/mac-help/open-a-mac-app-from-an-unidentified-developer-mh40616/mac) is much easier than running a bunch of shell commands to resign the application.