Bob, with which version of LC did you see this?
I had a look at the most current dp version of 10. If LC would require a certificate then there should be somewhere in the standalone settings a area where one could select an appropriate certificate. But that is not the case. What LC does for some time now when creating a macOS standalone is doing an ad-hoc code signing. Please do not ask me what that is, ;) but this kind of code signing seems not to require a certificate. The ad-hoc code signing is done in the stack revsaveasstandalone.livecodescript. Search for 'private command performAdHocCodesign' So there might some other problem and LC does come up with a misleading error message. Matthias > Am 28.02.2022 um 19:52 schrieb Bob Sneidar via use-livecode > <use-livecode@lists.runrev.com>: > > Hi Klaus. > > Actually the new LC versions do not create the standalone without those > certificates. That is the error dialog I get. If there is a way to disable > that feature that would be great! > > Bob S > > >> On Feb 28, 2022, at 10:18 , Klaus major-k via use-livecode >> <use-livecode@lists.runrev.com> wrote: >> >> Hi Bob, >> >>> Am 28.02.2022 um 18:18 schrieb Bob Sneidar via use-livecode >>> <use-livecode@lists.runrev.com>: >>> >>> Okay, so I am at the point that I cannot build apps without codesigning and >>> notarizing. Livecode will throw an error now if I try and don't have these >>> certificates installed. Great. >>> >>> So I have been going through the tutorial, and I see I have to be an Apple >>> Developer, which means I have to shell out yet another $100 per year. Fine, >>> I did that, even though my app is for internal consumption only. >>> >>> Now It appears that for me to get the certificates needed to create a Mac >>> standalone, I need xCode! Okay, I go to download xCode, and it will not >>> install because my MacOS is too old! 10.15.1 is apparently ancient! So I am >>> at the point now where I am asking myself, is this really worth it? After >>> all the back and forth on the list where people's certificates expire, or >>> the version of xCode they are forced to use isn't compatible with one thing >>> or another, is building Mac standalones really worth it? >>> >>> So my question is, do I really have to go through all this just to create a >>> Mac standalone from livecode? Or do these other utilities, >>> mrSignNotarizeHelperV3 for example, eliminate the need for all of that? >>> >>> Bob S >> >> you can still create a standalone with LC without any certificate etc.! >> >>> ...even though my app is for internal consumption only. >> >> >> But your user(s) need to check -> Allow downloads from: Appstore and trusted >> developers >> In the macOS system settings -> Security >> >> And after the they need to right-click your app and select "Open..." from >> the context menu >> and confirm once or twice that they really want to open that app. >> >> After that they can doubleclick the app furthermore like the used to. >> >> >> Best >> >> Klaus >> >> -- >> Klaus Major >> https://www.major-k.de >> https://www.major-k.de/bass >> kl...@major-k.de > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
