Thank you for the response, Etresoft. In all honesty, I did not see the the third line. I used to use the verification as references on the official Apple webpage for debugging notarization issue. - https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution/resolving_common_notarization_issues#3087735, which returns only the first two lines: codesign -vvv --deep --strict <my_lib.dylib> <my_lib.dylib>: valid on disk <my_lib.dylib>: satisfies its Designated Requirement But then saw the post from eskimo and though to give that at try, as well, and it seemed to return the same thing (which I now see it does not). The whole build process is fully automated and only this particular build has problems (without any error in the notarization plists returned by the various tools used in the process). The dylibs and exe file is zipped and sent to the notarization tool. In any case, I will use the verification suggested by eskimo in order to at least get a hint if the notarization may have failed and also do the smoke test as you suggested. However, it's a bit disappointing to see that automation is not supported for the verification and, more so, that there is no indication regarding this on the official Apple documentation

I'm running into the same issue. Maybe @eskimo can help, as this can potentially break a lot of automations. There were talks about softwareupdate being deprecated, but not much in the direction of offering an alternative to softwareupdate.