The signature of the binary is invalid

Question

Created May ’21

Replies 2

Boosts 0

Views 1.5k

Participants 2

After notarization installer package we have this error

{
"logFormatVersion": 1,
"jobId": "3e34a640-9cc1-4366-ac84-8f26c61c896d",
"status": "Invalid",
"statusSummary": "Archive contains critical validation errors",
"statusCode": 4000,
"archiveFilename": "connect_s.pkg.zip",
"uploadDate": "2021-05-17T21:48:14Z",
"sha256": "d18edb5b965570b2c9d5e14313c223a50b3c7ffef8f52594dc77dfbd3f108ecf",
"ticketContents": null,
"issues": [
{
"severity": "error",
"code": null,
"path": "connect_s.pkg.zip/connect_s.pkg/connect_s.pkg Contents/Payload/Applications/Connect (1000THVVLJLMNJ2UPSU7JJBBPHNLCN8LKGsaicloud)/messenger.app/Contents/MacOS/messenger",
"message": "The signature of the binary is invalid.",
"docUrl": null,
"architecture": "x86_64"
}
]
}

We sure that file was signed and even pass notarization

codesign --verify --verbose "messenger.app"
messenger.app: valid on disk
messenger.app: satisfies its Designated Requirement

We use Packages for create installer. And it works for other package that was created by Packages.

Boost

Answer 1

ericfrommurray OP

May ’21

Found issue. MacOS folder must contain only executable files

0

Answer 2

DTS Engineer OP

Apple

May ’21

MacOS folder must contain only executable files

Correct. See the Nested Code section of Technote 2206 macOS Code Signing In Depth for more background on this.

What happened here is that your non-code items in Contents/MacOS get signed as code. However, they can’t carry a code signature and thus the code signature ends up being stored in extended attributes. Such signatures are valid but can trigger other problems. This is the reason that TN2206 is so adamant about nesting code in code locations and data in data locations.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0