Project: appceleratorstudio
Issue TISTUD-6965: Sign OS X application with "Version 2" of developer signature
From Apple: 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. For more details, read “Code Signing changes in OS X Mavericks” and “Changes in   OS X 10.9.5 and Yosemite Developer Preview 5” in OS X: https://developer.apple.com/library/mac/technotes/tn2206/_index.html See also related bugs in Eclipse: * https://bugs.eclipse.org/bugs/show_bug.cgi?id=445015 * https://bugs.eclipse.org/bugs/show_bug.cgi?id=445050
Story points: 8