I have been code signing my py2app Python applications for over 5 years. Recently, my application notarizes and staples with no errors. However, when I try to verify the signature I get the above error. I do not see any errors in the appropriate notary log file. Can't figure out how to post the log file. The associated ID is: eb78c6b0-cdd2-414f-9dd3-24315a27d457
Can anyone point me to an appropriate reference ?
That message corresponds to errSecCSInvalidObjectRef (-67071). That’s an obscure one. I’ve been supporting Mac coded signing for almost a decade and I’ve never seen it before. Well done!
Can't figure out how to post the log file.
You can post log files as text attachments. I have info on how to do that in Posting a Crash Report. Its focus is on crash reports, but the process for posting a text attachment is the same in both cases.
However, the notary log is unlikely to help here because, as you say, the app notarises successfully. Rather, this is a code signing error on your local Mac.
when I try to verify the signature I get the above error.
How are you doing that? Normally I’d verify a signature like so:
% codesign -v --deep --strict /path/to/my.app
Is that what you’re doing?
As to the potential causes of errSecCSInvalidObjectRef, there are very few. Most of them will throw that error and also log more details to the system log. So, you can often learn more by:
See Your Friend the System Log for lots of hints and tips on how to use the system log effectively.
Alternatively, if you’re able to post a URL to a place where I can download your app, I’d be happy to take a look.
See tip 14 in Quinn’s Top Ten DevForums Tips for advice on how to post links.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"