Building a Standalone MacOS App in 9.6.1
Andrew at MidWest Coast Media
andrew at midwestcoastmedia.com
Wed Jan 6 12:30:19 EST 2021
So far I have been able to explain to my limited client base that this can be side stepped, and they are ok with that for now (AKA don’t want to pay for the necessary upgrade that will be needed).
If you double-click to open the app you will get a notice that the app isn’t notarized and you can’t launch. If you right-click (ctrl-click) on the app and select Open rather than double-clicking to open, your user will be given notice that the app isn’t notarized but will allow them to launch anyway.
I don’t see the notice when developing personal apps for use on my own machine. I’m assuming this is because the Developer key (or certificate?) is on my keychain so the app is somewhat verified.
> Date: Wed, 6 Jan 2021 16:17:23 +0100
> From: Tore Nilsen <tore.nilsen at me.com>
> To: How to use LiveCode <use-livecode at lists.runrev.com>
> Subject: Re: Building a Standalone MacOS App in 9.6.1
> Message-ID: <84BE53BE-AFD1-4FA2-B874-5D22B4EDA7EF at me.com>
> Content-Type: text/plain; charset=us-ascii
>> 6. jan. 2021 kl. 15:48 skrev Paul Dupuis via use-livecode <use-livecode at lists.runrev.com>:
>> macOS Catalina or Big Sur apps have to be code signed AND notarized. You must have the command line tools installed and there is a non-trivial number of commands you have to execute to prepare you app for code signing, then code sign it, and then notarize it, including obtaining an app specific password from Apple.
>> Livecode has a pretty decent tutorial on their web site on the whole lengthy process.
> I can happily build a MacOS app without code signing or notarizing the app from Big Sur and Catilina. I guess this is needed for an iOS app, but then again you cannot build an iOS app with LiveCode Community
> Best regards
> Tore Nilsen
More information about the use-livecode