I have run into the same issue just now. Worked for all previous versions.

"sudo kmutil clear-staging" followed by reboot might help.

Xcode installs Python 3.x

Check out the threads on the MacRumors forums about running newer versions of macOS on unsupported hardware.

I think the spirit of account deletion is GDPR - privacy. It's related to the legal requirement that the user can have all server based data tied to an identity deleted.

This is the dev beta. I reinstalled the Developer Beta Access Utility and that triggered the update.

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

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

What exactly does this mean, since the same Developer ID: Installer and : Application works in all other combos? source=Unnotarized Developer ID

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" } ] }

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.

Oops. Sorry. I hate that when people only answer part of a question and here I am doing that. But that ****** is gone - so many attempts, to few moments in life. Here is a fresh one: In target folder prior DropDMG (used for quick experimentation, I later bash a script for the QA builds): % spctl -a -vvv emWave\ Pro.app emWave Pro.app: accepted source=Developer ID origin=Developer ID Application: HeartMath LLC (GMZ3FT78RD) Build DMG and sign, mount, and check signature on it: % spctl -a -vvv emWave\ Pro.app emWave Pro.app: accepted source=Developer ID origin=Developer ID Application: HeartMath LLC (GMZ3FT78RD)``` Send off to notarization: https://osxapps-ssl.itunes.apple.com/itunes-assets/Enigma112/v4/68/cd/cc/68cdcc9c-0579-6c35-0d12-e39db9a94e5c/developer_log.json?accessKey=1659643471_4931801388376640712_m64RSh33h2i77lk0c2I0Gnoo%2BBssMltizD7ye7Qdh4BL9n4k6%2BtNEjergyK7I5c5jD%2FSd%2FZzpRxhXhuWv9d11bHUFwSMNuYBijbhQUeqOywgbJkVehljacihBej%2Bc6D6qe0iQgGO877nzBVDx6tuetRH9y8XeJpJV0Kr9y6ZFdE%3D    RequestUUID: 256cc0c2-7eb2-4b8d-b54f-94b52b2a05f6 { "logFormatVersion": 1, "jobId": "256cc0c2-7eb2-4b8d-b54f-94b52b2a05f6", "status": "Invalid", "statusSummary": "Archive contains critical validation errors", "statusCode": 4000, "archiveFilename": "emWave+Pro.dmg", "uploadDate": "2022-08-02T13:59:15Z", "sha256": "d0240c577486929536bb8c4f72b0749023d4c2978fdca525ab03214c85ce9a08", "ticketContents": null, "issues": [ { "severity": "error", "code": null, "path": "emWave+Pro.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": "emWave+Pro.dmg/emWave Pro.app/Contents/MacOS/emWaveMac", "message": "The signature of the binary is invalid.", "docUrl": null, "architecture": "arm64" } ] } Remount DMG and check, because ... superstition: % spctl -a -vvv emWave\ Pro.app emWave Pro.app: accepted source=Developer ID origin=Developer ID Application: HeartMath LLC (GMZ3FT78RD) Notarize the app by itself from the source folder, since the DMG is RO. My script returns: [...] Downloaded ticket has been stored at file:///var/folders/1z/zdzqgk4s22s2wjy7ds9d21qm0000gn/T/93dc7955-57cf-4749-ae1c-14662a4fd3dd.ticket. The validate action worked! As I wrote, if I drop a signed installer into the same folder, it works. All this is using altool. I am converting scripts to notarize, but that should not make a difference.

It looks like only ONE system on a system with multiple boots is alliowd a wallet.

Oops. Thanks. That's what I used to use until reading some Apple docs. Everything's valid. I had to snip some stuff due to forum character limits. % codesign -v -vvv --strict --deep /Volumes/emWave\ Pro/emWave\ Pro.app --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtCore.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtCore.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtDBus.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtDBus.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtGui.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtGui.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtMultimedia.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtMultimedia.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtMultimediaQuick.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtMultimediaQuick.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtMultimediaWidgets.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtMultimediaWidgets.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtNetwork.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtNetwork.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtOpenGL.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtOpenGL.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtPdf.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtPdf.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtPositioning.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtPositioning.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtPrintSupport.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtPrintSupport.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtQml.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtQml.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtQmlModels.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtQmlModels.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtQuick.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtQuick.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtQuickWidgets.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtQuickWidgets.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtSerialPort.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtSerialPort.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtSql.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtSql.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtSvg.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtSvg.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtVirtualkeyboard.framework/Versions/Current/. [...] SNIPP!!!! --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtWebEngineWidgets.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtWebEngineWidgets.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtWebView.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtWebView.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtWidgets.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtWidgets.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtXml.framework/Versions/Current/. --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/QtXml.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/Sparkle.framework/Versions/Current/. --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/Sparkle.framework/Versions/Current/Autoupdate --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/Sparkle.framework/Versions/Current/Autoupdate --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/Sparkle.framework/Versions/Current/Updater.app --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/Sparkle.framework/Versions/Current/Updater.app --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/Sparkle.framework/Versions/Current/XPCServices/org.sparkle-project.Downloader.xpc --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/Sparkle.framework/Versions/Current/XPCServices/org.sparkle-project.Downloader.xpc --prepared:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/Sparkle.framework/Versions/Current/XPCServices/org.sparkle-project.InstallerLauncher.xpc --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/Sparkle.framework/Versions/Current/XPCServices/org.sparkle-project.InstallerLauncher.xpc --validated:/Volumes/emWave Pro/emWave Pro.app/Contents/Frameworks/Sparkle.framework/Versions/Current/. /Volumes/emWave Pro/emWave Pro.app: valid on disk /Volumes/emWave Pro/emWave Pro.app: satisfies its Designated Requirement

Hypothesis: I noted on going back to booting Monterey that the security policy had ALWAYS been set back to defaults on the Monterey System disk. I normally keep it in relaxed security to enable Developer Signed Extensions. This leads me to believe the installer sets the main disk security policy for install instead of the target disk. I might try disabling all security on that disk and attempt to update,