#Stclairsoft go64 archive

On Dec 7, 2020, at 4:19 PM, Jon Gotow wrote: On Dec 7, 2020, at 9:57 AM, Mark Allan wrote: On Dec 7, 2020, at 3:21 PM, Mark Allan wrote: No I hadn't checked that tool.but I have now, and it says 'YES' ie it's signed correctly, so unfortunately I'm no further forward. On Dec 7, 2020, at 1:21 PM, Mark Allan wrote: Have you tried that? Does it report anything useful? TN2206 ( ) makes reference to using the `check-signature` tool ( ) to validate package signatures. I can't speak to what might be the problem, but I've been reading about code signing and notarization recently in an effort to better understand how it all works at a lower level, so I'm interested in what you find out. Is anyone aware of any changes to pkgbuild and productbuild which might have caused this? The man pages don't reference anything new that might be relevant, so I'm stuck. The signature is valid and I can see this in macOS 11 and 10.15 when clicking the certificate icon in the upper right corner of the window, so I'm not sure what's going on. Get a new copy of the package and try again. The package may have been corrupted or tampered with. Installer_signed.pkg can't be installed because its digital signature is invalid. When I try to open the installer on the older OSes, I'm presented with the following error message: pkg installer file along with all the other elements of the app.įor the last few years this has worked fine, but for some reason I'm now unable to open the resulting pkg file on macOS 10.10 and 10.11.

#Stclairsoft go64 archive

I have a script which Xcode runs as a post-action during the archive phase which takes my compiled app, and generates a signed.