Awaiting assistance from a DTS engineer regarding a peculiar notarization issue.

Hello,

Our company's software successfully passes the notarization process when exported through Xcode Archive and compressed into a zip file. However, it fails notarization when packaged into a pkg using the Packages software (version 1.2.10), consistently returning the error "The signature of the binary is invalid." We need assistance to resolve this issue.

Here are some specific details on the signature statuses and notarization information:

xcrun stapler validation: Successful

xcrun stapler validate Maxi\ PC\ Suite.app Processing: /Users/autel/Desktop/test11/files/Maxi PC Suite.app The validate action worked! pkgutil signature check: Successful

pkgutil --check-signature Maxi\ PC\ Suite.pkg

Package "Maxi PC Suite.pkg": Status: signed by a developer certificate issued by Apple for distribution Signed with a trusted timestamp on: 2025-01-09 08:09:17 +0000 Certificate Chain: 1. Developer ID Installer: Autel Intelligent Technology Co., Ltd. (MEXQ8HADL9) Expires: 2027-02-01 22:12:15 +0000 SHA256 Fingerprint: B7 F7 AC 05 19 78 CB 5D 66 C1 11 95 EE C9 2E 31 B9 AA BD F5 32 E4 B6 4D 8D 0D 06 04 EE BC 1B 5A ------------------------------------------------------------------------ 2. Developer ID Certification Authority Expires: 2027-02-01 22:12:15 +0000 SHA256 Fingerprint: 7A FC 9D 01 A6 2F 03 A2 DE 96 37 93 6D 4A FE 68 09 0D 2D E1 8D 03 F2 9C 88 CF B0 B1 BA 63 58 7F ------------------------------------------------------------------------ 3. Apple Root CA Expires: 2035-02-09 21:40:36 +0000 SHA256 Fingerprint: B0 B1 73 0E CB C7 FF 45 05 14 2C 49 F1 29 5E 6E DA 6B CA ED 7E 2C 68 C5 BE 91 B5 A1 10 01 F0 24 pkg notarization: Failed

xcrun notarytool submit Maxi\ PC\ Suite.pkg --apple-id *** --team-id *** --password *** --wait Conducting pre-submission checks for Maxi PC Suite.pkg and initiating connection to the Apple notary service... Submission ID received id: ccbf6330-b64a-4b42-87c0-b5db1fe25b2d Upload progress: 100.00% (3.42 MB of 3.42 MB)
Successfully uploaded file id: ccbf6330-b64a-4b42-87c0-b5db1fe25b2d path: /Users/autel/Desktop/test11/build/Maxi PC Suite.pkg Waiting for processing to complete. Current status: Invalid. Processing complete id: ccbf6330-b64a-4b42-87c0-b5db1fe25b2d status: Invalid Detailed notarization failure information:

xcrun notarytool log ccbf6330-b64a-4b42-87c0-b5db1fe25b2d --keychain-profile "PC_Suit_Mac" { "logFormatVersion": 1, "jobId": "ccbf6330-b64a-4b42-87c0-b5db1fe25b2d", "status": "Invalid", "statusSummary": "Archive contains critical validation errors", "statusCode": 4000, "archiveFilename": "Maxi PC Suite.pkg", "uploadDate": "2025-01-09T08:18:22.374Z", "sha256": "0d1bd15e5c30bc890d20086de865739d01e131e34386b73ac20f8a5d52229906", "ticketContents": null, "issues": [ { "severity": "error", "code": null, "path": "Maxi PC Suite.pkg/Maxi_PC_Suite.pkg Contents/Payload/Applications/Maxi PC Suite.app/Contents/MacOS/Maxi PC Suite", "message": "The signature of the binary is invalid.", "docUrl": "https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution/resolving_common_notarization_issues#3087735", "architecture": "x86_64" } ] } We are looking for advice on how to resolve the error related to the invalid binary signature during the pkg notarization process.

Thank you.

Answered by DTS Engineer in 820655022

Regarding your formatting issue:

  • Sorry your reply got deleted. That wasn’t my doing.

  • DevForums does let you edit posts, but only for a short time after creating them. The last time I checked this was an hour. After that they’re locked.


Regarding your main issue, you wrote:

However, it fails notarization when packaged into a pkg using the Packages software

That’s the third-party Packages app, right? If so, DTS can’t help you with that. You’ll need to escalate this with the app’s developer.

Before doing that, however, I recommend that you run a quick test notarisation with Apple’s tools. For an example of how to do this, see Packaging Mac software for distribution. If that works and your third-party apps fails, then the escalation path is clear. OTOH, if things continue to fail when you use productbulid, that’s something I can help you with.

IMPORTANT I’m not suggesting that you move to productbuild for your shipping app. The goal here is purely diagnostic.

Share and Enjoy

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

Regarding your formatting issue:

  • Sorry your reply got deleted. That wasn’t my doing.

  • DevForums does let you edit posts, but only for a short time after creating them. The last time I checked this was an hour. After that they’re locked.


Regarding your main issue, you wrote:

However, it fails notarization when packaged into a pkg using the Packages software

That’s the third-party Packages app, right? If so, DTS can’t help you with that. You’ll need to escalate this with the app’s developer.

Before doing that, however, I recommend that you run a quick test notarisation with Apple’s tools. For an example of how to do this, see Packaging Mac software for distribution. If that works and your third-party apps fails, then the escalation path is clear. OTOH, if things continue to fail when you use productbulid, that’s something I can help you with.

IMPORTANT I’m not suggesting that you move to productbuild for your shipping app. The goal here is purely diagnostic.

Share and Enjoy

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

Awaiting assistance from a DTS engineer regarding a peculiar notarization issue.
 
 
Q