Mark,
When I create a new, empty test stack and save as a standalone using versions 
9.6.0, 9.6.1 and 9.6.2, I right-click the resulting app to show contents and 
there is a folder “_CodeSignature” and inside that is a “CodeResources” file. 
When I build a test standalone with LC 9.5.1 that folder is not present. So LC 
must have started codesigning as you described starting with 9.6.0.

I can build a standalone in 9.6.1, codesign with AppWrapper and it notaries and 
runs fine. It’s when I do the build with 9.6.2 - it will run before I codesign 
with AppWrapper but after I codesign with AppWrapper - then it crashes on 
startup. It is a Levure-based app. If I create an empty test stack, build with 
9.6.2, then codesign with AppWrapper it will open without a problem. So it 
looks like something specific to Levure or some combination of Levure, the 
version of my X-code (I’m on Mojave running X-Code 10.1 it looks like.) and LC 
9.6.2.

Marty


> On Feb 3, 2021, at 1:17 PM, Mark Talluto via use-livecode 
> <[email protected]> wrote:
> 
> LiveCode codesigns their inner parts so they can run on our desktops. We are 
> still required to codesign and notarize our standalones. I too use AppWrapper 
> and have been able to process them fully without errors. 
> 
> This is the email from Apple explaining the new certificate:
> 
> Starting January 28, 2021, the digital certificates you use to sign your 
> software for installation on Apple devices, submit apps to the App Store, and 
> connect to certain Apple services will be issued from a new intermediate 
> Apple Worldwide Developer Relations certificate (expiring 2030). This new 
> intermediate certificate will not affect the availability or functionality of 
> apps you’re already distributing on the App Store. And you can continue to 
> use your existing certificates until they expire. 
> 
> If you’re running Xcode 11.4.1 or later, you’ll receive the updated 
> certificate automatically when you sign an app after January 28, 2021. If 
> you’re running an earlier release of Xcode and need to generate new 
> certificates, download and install the new intermediate certificate and 
> utilize the command line to sign your app. You can also archive your build 
> with your existing Xcode version and sign it for distribution with Xcode 
> 11.4.1 or later. 
> 
> The current intermediate certificate (expiring in 2023), will continue to 
> issue certain Apple services certificates, including Apple Push Notification 
> service (APNs) SSL certificates and Apple Wallet pass signing certificates. 
> Keep both versions installed on your development systems and servers until 
> later this year. 
> 
> Learn more about upcoming certificate updates for Apple services. 
> <https://c.apple.com/r?v=2&la=en&lc=usa&a=yI6DvqeHGx8Uu2vh7OcF6nanlAxl6kDMv8nG7zaHtQ99osJFtvwJEYBlgUzgHh6dbyk7A9hhPJTIy9r%2BhjMuFrjP6NNq3y8jpL%2FmGvU3LIY%3D&ct=a4C8t168s2>
>  
> 
> Best regards,
> Apple Developer Relations
> 
> 
> Best regards,
> 
> Mark Talluto
> livecloud.io <http://livecloud.io/>
> nursenotes.net <http://nursenotes.net/>
> canelasoftware.com <http://www.canelasoftware.com/>
> 


_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to