1

I am signing an OS X app using my Developer ID Application certificate; it is a self-hosted app. The build server is an El Capitan machine (10.11.6).

The app passes validation on Mavericks, Yosemite, El Capitan and Sierra. However, on Mtn Lion I am informed that the app has been damaged or tampered and I get the option to send it to Trash. Sure enough, a codesign -dv /Applications/Whatever.app shows the same result. Trying to install RB App Checker Lite, I am informed that this old OS is not supported, and I was unable to find an older version, to see whether it would show me more details.

Is this behavior normal / documented anywhere?

I do know that Mavericks introduced a new type of signature, and Mtn Lion's Gatekeeper is expecting a v1. I couldn't find anything more relevant than an old (2014) announcement from Apple, regarding Mac App Store submission rules changes:

Beginning November 1, 2014, apps submitted to the Mac App Store must be signed with signatures created with OS X Mavericks 10.9 or later (v2 signatures). Apps without v2 signatures will be automatically rejected on upload.

[...]

Apps signed with v2 signatures will work on older versions of OS X.

If there is something I am missing and/or a workaround, I would gladly acknowledge and act on / adopt it, instead of asking customers to alter security settings on their Macs. Thank you.

You must log in to answer this question.

Browse other questions tagged .