To build a Mac App, you need to have Xcode tools on your Mac. You don't need to use them. You don't even need to know about them. They just have to be there. If you've never installed Xcode they won't be there. See this lesson:
https://lessons.livecode.com/m/4603/l/1353263-i-m-getting-an-error-when-trying-to-save-as-standalone-on-mac <https://lessons.livecode.com/m/4603/l/1353263-i-m-getting-an-error-when-trying-to-save-as-standalone-on-mac> Best Regards, Heather Heather Laine Customer Services Manager LiveCode Ltd www.livecode.com > On 1 Mar 2022, at 00:35, Bob Sneidar via use-livecode > <use-livecode@lists.runrev.com> wrote: > > I am getting, "Adding ad-hoc signature failed with error: <path to > standalone> replacing existing signature xcrun: error: invalid active > developer path (/library/developer/commandlinetools), missing xcrun at...the > code sign_allocate helper tool cannot be found in subcomponent <path to > standalone>/Contents/MacOS/revsecurity.dylib > > I think I will attempt to download the command line tools and see if that > fixes it. > > The ad-hoc certificate is (if I am not mistaken) a self signed certificate. > > Bob S > > >> On Feb 28, 2022, at 13:40 , General 2018 via use-livecode >> <use-livecode@lists.runrev.com> wrote: >> >> I think some misunderstandings …. >> >> You can build LC standalone with no certifications on MacOS desktop. >> >> The issue comes when you wish to codesign and notarise for distribution >> downloads from web etc. To do any codesigning and notarization with apple >> you need the certificates and be a member of the development program. >> >> The standalone will run fine but without apple codesign and notarization but >> the latest MacOS gatekeeper will give warnings etc on MacOS desktop. >> >> For IOS the certified route is a must. >> >> Regards >> Camm >> >>> On 28 Feb 2022, at 21:25, Craig Newman via use-livecode >>> <use-livecode@lists.runrev.com> wrote: >>> >>> All. >>> >>> I am not sure I am following this thread correctly. Is the issue that some >>> sort of certificate is now required for creating a standalone for desktop? >>> >>> Craig >>> >>>> On Feb 28, 2022, at 4:12 PM, William Prothero via use-livecode >>>> <use-livecode@lists.runrev.com> wrote: >>>> >>>> Dealing with Apple certificates is the most onerous part of building a >>>> standalone. I really wish the livecode team could help address this issue >>>> and help us out. >>>> >>>> best, >>>> Bill >>>> >>>> William A Prothero >>>> >>>>>> On Feb 28, 2022, at 12:56 PM, Tom Glod via use-livecode >>>>>> <use-livecode@lists.runrev.com> wrote: >>>>> >>>>> I use a mac in the cloud ..... but i have yet to do any signing .... I >>>>> gotta get myself to do it this week. thanks for the reminder...i've been >>>>> putting it off like its math homework only worse. :D >>>>> >>>>> https://www.macincloud.com/ >>>>> >>>>>> On Mon, Feb 28, 2022 at 3:38 PM matthias rebbe via use-livecode < >>>>>> use-livecode@lists.runrev.com> wrote: >>>>>> >>>>>> 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 >>>>>> >>>>> _______________________________________________ >>>>> 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 >>> >>> >>> _______________________________________________ >>> 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 > > _______________________________________________ > 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
