AW: OS X codesigning best practise?
tbodine
bodine at bodinetraininggames.com
Tue Sep 16 15:46:25 EDT 2014
>From Apple Developer news email received Sept. 16, 2014:
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.
If you build code with an older version of OS X, use OS X Mavericks 10.9 or
later to sign your app and create v2 signatures using the codesign tool.
Structure your bundle according to the signature evaluation requirements for
OS X Mavericks 10.9 or later. Considerations include:
* Signed code should only be placed in directories where the system
expects to find signed code.
* Resources should not be located in directories where the system
expects to find signed code.
* The --resource-rules flag and ResourceRules.plist are not supported.
Make sure your current and upcoming releases work properly by testing on OS
X Mavericks 10.9.5 and OS X Yosemite 10.10 Developer Preview 5 or later.
Apps signed with v2 signatures will work on older versions of OS X.
--
View this message in context: http://runtime-revolution.278305.n4.nabble.com/OT-OS-X-codesigning-best-practise-tp4683096p4683311.html
Sent from the Revolution - User mailing list archive at Nabble.com.
More information about the use-livecode
mailing list