Post

Replies

Boosts

Views

Activity

Reply to Notarization failures with DMG wrapped app
Quinn Quinn, Thanks for your help. I tried two methods. Both work with our Installer PKG: Script excerpt - we set up a folder and: hdiutil create -srcfolder "$SRC_DIR" -volname "$VOLNAME" -fs HFS+ \ -fsargs "-c c=64,a=16,e=16" -format UDRW "$TMP_DMG" The other uses dropDMG from that folder. All my build scripts use a form of 'ditto' to move or copy stuff.
Topic: Code Signing SubTopic: Notarization Tags:
Aug ’22
Reply to Notarization failures with DMG wrapped app
Here is my validation for the app: emWave Pro.app: accepted source=Developer ID origin=Developer ID Application: HeartMath LLC (GMZ3FT78RD) Validation for the DMG shows Unnotarized: spctl verification: emWavePro.dmg: rejected source=Unnotarized Developer ID origin=Developer ID Application: HeartMath LLC (GMZ3FT78RD) Here is what I get back from the portal: { "logFormatVersion": 1, "jobId": "5b0c0eed-7a61-45ed-8a85-94fe16ec296e", "status": "Invalid", "statusSummary": "Archive contains critical validation errors", "statusCode": 4000, "archiveFilename": "emWavePro.dmg", "uploadDate": "2022-07-29T14:46:14Z", "sha256": "1bb8d490311e237280b29c28831c5078ae628ad1d54e5e70c0ffe8538ad23c42", "ticketContents": null, "issues": [ { "severity": "error", "code": null, "path": "emWavePro.dmg/emWave Pro.app/Contents/MacOS/emWaveMac", "message": "The signature of the binary is invalid.", "docUrl": null, "architecture": "x86_64" }, { "severity": "error", "code": null, "path": "emWavePro.dmg/emWave Pro.app/Contents/MacOS/emWaveMac", "message": "The signature of the binary is invalid.", "docUrl": null, "architecture": "arm64" } ] }
Topic: Code Signing SubTopic: Notarization Tags:
Jul ’22
Reply to Notarization failures with DMG wrapped app
Checking the app on the DMG I get this: % codesign -d -vv /Volumes/emWave\ Pro/emWave\ Pro.app  Executable=/Volumes/emWave Pro/emWave Pro.app/Contents/MacOS/emWaveMac Identifier=com.heartmath.emwave Format=app bundle with Mach-O universal (x86_64 arm64) CodeDirectory v=20500 size=112672 flags=0x10000(runtime) hashes=3510+7 location=embedded Signature size=8997 Authority=Developer ID Application: NNNNNNNN (GMxxxxxxxx) => obscured Authority=Developer ID Certification Authority Authority=Apple Root CA Timestamp=Jul 28, 2022 at 5:48:25 PM Info.plist entries=30 TeamIdentifier=GMZxxxxxxxx Runtime Version=12.3.0 Sealed Resources version=2 rules=13 files=1241 Internal requirements count=1 size=180
Topic: Code Signing SubTopic: Notarization Tags:
Jul ’22
Reply to Notarization failures with DMG wrapped app
Quinn Quinn, Thanks for your help. I tried two methods. Both work with our Installer PKG: Script excerpt - we set up a folder and: hdiutil create -srcfolder "$SRC_DIR" -volname "$VOLNAME" -fs HFS+ \ -fsargs "-c c=64,a=16,e=16" -format UDRW "$TMP_DMG" The other uses dropDMG from that folder. All my build scripts use a form of 'ditto' to move or copy stuff.
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
Aug ’22
Reply to Notarization failures with DMG wrapped app
Here is my validation for the app: emWave Pro.app: accepted source=Developer ID origin=Developer ID Application: HeartMath LLC (GMZ3FT78RD) Validation for the DMG shows Unnotarized: spctl verification: emWavePro.dmg: rejected source=Unnotarized Developer ID origin=Developer ID Application: HeartMath LLC (GMZ3FT78RD) Here is what I get back from the portal: { "logFormatVersion": 1, "jobId": "5b0c0eed-7a61-45ed-8a85-94fe16ec296e", "status": "Invalid", "statusSummary": "Archive contains critical validation errors", "statusCode": 4000, "archiveFilename": "emWavePro.dmg", "uploadDate": "2022-07-29T14:46:14Z", "sha256": "1bb8d490311e237280b29c28831c5078ae628ad1d54e5e70c0ffe8538ad23c42", "ticketContents": null, "issues": [ { "severity": "error", "code": null, "path": "emWavePro.dmg/emWave Pro.app/Contents/MacOS/emWaveMac", "message": "The signature of the binary is invalid.", "docUrl": null, "architecture": "x86_64" }, { "severity": "error", "code": null, "path": "emWavePro.dmg/emWave Pro.app/Contents/MacOS/emWaveMac", "message": "The signature of the binary is invalid.", "docUrl": null, "architecture": "arm64" } ] }
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
Jul ’22
Reply to Notarization failures with DMG wrapped app
What exactly does this mean, since the same Developer ID: Installer and : Application works in all other combos? source=Unnotarized Developer ID
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
Jul ’22
Reply to Notarization failures with DMG wrapped app
Checking the app on the DMG I get this: % codesign -d -vv /Volumes/emWave\ Pro/emWave\ Pro.app  Executable=/Volumes/emWave Pro/emWave Pro.app/Contents/MacOS/emWaveMac Identifier=com.heartmath.emwave Format=app bundle with Mach-O universal (x86_64 arm64) CodeDirectory v=20500 size=112672 flags=0x10000(runtime) hashes=3510+7 location=embedded Signature size=8997 Authority=Developer ID Application: NNNNNNNN (GMxxxxxxxx) => obscured Authority=Developer ID Certification Authority Authority=Apple Root CA Timestamp=Jul 28, 2022 at 5:48:25 PM Info.plist entries=30 TeamIdentifier=GMZxxxxxxxx Runtime Version=12.3.0 Sealed Resources version=2 rules=13 files=1241 Internal requirements count=1 size=180
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
Jul ’22
Reply to Notarization failures with DMG wrapped app
For the DMG I get: % spctl -a -t open -vvv --context context:primary-signature *.dmg emWave Pro.dmg: rejected source=Unnotarized Developer ID origin=Developer ID Application: HeartMath LLC (GMZxxxxx) code-block
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
Jul ’22
Reply to Ventura Beta 4 is not showing up in Preferences on Mac Studio
This is the dev beta. I reinstalled the Developer Beta Access Utility and that triggered the update.
Topic: Community SubTopic: Apple Developers Tags:
Replies
Boosts
Views
Activity
Jul ’22
Reply to Macbook too old.
Check out the threads on the MacRumors forums about running newer versions of macOS on unsupported hardware.
Replies
Boosts
Views
Activity
Jun ’22
Reply to Questions about default python version for MacBook Pro 2021 m1 pro
Xcode installs Python 3.x
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jun ’22