I’m using SD 8.07 in a Mojave VM to write apps that target a suite of 32 and 64 bit Helix products.
Post Nov 2023 the scripts themselves need to be signed and notarised in the Host OS, Sonoma.
I have a Developer ID Application certificate installed in Sonoma that verifies and has an expiry date of Feb 2027.
For months now, at least up until late April 2024 I have been able to sign and notarise any app with this setup by simply selecting “Submit…”
This week though the process is failing e.g.
22:15:38.920: {
“logFormatVersion”: 1,
“jobId”: “5d618dac-854e-450e-b82c-a4b35a62cf60”,
“status”: “Invalid”,
“statusSummary”: “Archive contains critical validation errors”,
“statusCode”: 4000,
“archiveFilename”: “minminlights.zip”,
“uploadDate”: “2024-05-28T12:14:38.894Z”,
“sha256”: “727af4cd360a04e4e41d0b12c0d9e3d82413bffd5860fca9c4e8a75edd3c23ad”,
“ticketContents”: null,
“issues”: [
{
“severity”: “error”,
“code”: null,
“path”: “/minminlights.app/Contents/MacOS/applet”,
“message”: “The signature of the binary is invalid.”,
“docUrl”: “Resolving common notarization issues | Apple Developer Documentation”,
“architecture”: “i386”
},
{
“severity”: “error”,
“code”: null,
“path”: “/minminlights/Contents/MacOS/applet”,
“message”: “The signature of the binary is invalid.”,
“docUrl”: “Resolving common notarization issues | Apple Developer Documentation”,
“architecture”: “x86_64”
}
]
}
I followed the documentation link and ran the tests recommended for the error with these results:
% codesign --verify --deep --strict --verbose=2 /minminlights
/minminlights: valid on disk
/minminlights: satisfies its Designated Requirement
From here I’m at a loss how to proceed with two issues
- Why is the binary regarded as invalid and what remedy is recommended?
- How do I get it notarised for the ARM architecture - or don’t I need to?
TIA
Lee