Post

Replies

Boosts

Views

Activity

Reply to notary tool fails on same file that altool notarizes successfully
I'm posting this here because I believe it falls within the same use case. But what do I know! Using terminal Xcode I am able to harden, notarize, pkg and validate my app for the distribution via the App Store, although I have not yet uploaded to the App Store. Process #1: Harden myApp using ID: Developer ID Application Zip myApp Notarize myApp using altool Pkg myApp using productbuild ID: 3rd Party Mac Developer Installer Validate myApp for compatibility with App Store using altool. Test installing myApp using the pkg. Success. Attempting to notarize and pkg myApp using Xcode notarytool produces (two) different results depending on the ID used. Process #2: Harden myApp using ID: Developer ID Application Pkg myApp using productbuild ID: 3rd Party Mac Developer Installer Notarize pkg generates a validation error:     {       "severity": "error",       "code": null,       "path": "myApp.pkg",       "message": "The binary is not signed with a valid Developer ID certificate.",       "docUrl": null,       "architecture": null     } Process #3: Harden myApp using ID: Developer ID Application Pkg myApp using productbuild ID: Developer ID Installer Notarize pkg. Successfully { Conducting pre-submission checks for myApp.pkg and initiating connection to the Apple notary service... Submission ID received   id: 610ca3ff-e587-4434-xxxx Successfully uploaded file153 MB of 153 MB)       id: 610ca3ff-e587-4434-xxxx   path: myApp Waiting for processing to complete. Current status: Accepted..................... Processing complete   id: 610ca3ff-e587-4434-xxxx   status: Accepted } Validate myApp.pkg using altool --validate-app errors for it requires the pkg to be signed with 3rd Party Mac Developer Installer. I need to be able to notarize and pkg myApp for the App Store.   Thanks for being here: Be well
Jul ’22