Into the future

[Bob Sneidar via use-livecode]

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


___
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

Re: Into the future

[Paul Dupuis via use-livecode]

No, you really have to go through all of that. The few helper stacks out 
there are just front ends (using the shell command to call command line 
utilities from xcode) that make it easier once you have everything set up.


Yes, it sucks.


On 2/28/2022 12:18 PM, Bob Sneidar via use-livecode wrote:

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


___
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

Re: Into the future

[Bob Sneidar via use-livecode]

It occurs to me that this may drive a lot of hobbyist Livecoders away, and 
discourage others from coming onboard. There ought to be some kind of 
disclaimer on the website, since it is a paid product only now. I'd be a bit 
miffed if I bought an application for developing new apps and didn't know that 
there would be more cash outlay required before it would work. 

Bob S


> On Feb 28, 2022, at 09:25 , Paul Dupuis via use-livecode 
>  wrote:
> 
> No, you really have to go through all of that. The few helper stacks out 
> there are just front ends (using the shell command to call command line 
> utilities from xcode) that make it easier once you have everything set up.
> 
> Yes, it sucks.
> 
> 
> On 2/28/2022 12:18 PM, Bob Sneidar via use-livecode wrote:
>> 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
>> 
>> 
>> ___
>> 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

Re: Into the future

[Bob Sneidar via use-livecode]

I guess the question now becomes, what is the last Livecode app that can create 
standalones without requiring these certificates? I may need to plant my flag 
there and go no further. 

Bob S


> On Feb 28, 2022, at 09:36 , Bob Sneidar via use-livecode 
>  wrote:
> 
> It occurs to me that this may drive a lot of hobbyist Livecoders away, and 
> discourage others from coming onboard. There ought to be some kind of 
> disclaimer on the website, since it is a paid product only now. I'd be a bit 
> miffed if I bought an application for developing new apps and didn't know 
> that there would be more cash outlay required before it would work. 
> 
> Bob S
> 
> 
>> On Feb 28, 2022, at 09:25 , Paul Dupuis via use-livecode 
>>  wrote:
>> 
>> No, you really have to go through all of that. The few helper stacks out 
>> there are just front ends (using the shell command to call command line 
>> utilities from xcode) that make it easier once you have everything set up.
>> 
>> Yes, it sucks.
>> 
>> 
>> On 2/28/2022 12:18 PM, Bob Sneidar via use-livecode wrote:
>>> 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
>>> 
>>> 
>>> ___
>>> 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

Re: Into the future

[Paul Dupuis via use-livecode]

It isn't really a LiveCode ting. This is Apple placing these 
requirements on their developers no matter what language you write code 
in for the macOS.


On 2/28/2022 12:43 PM, Bob Sneidar via use-livecode wrote:

I guess the question now becomes, what is the last Livecode app that can create 
standalones without requiring these certificates? I may need to plant my flag 
there and go no further.

Bob S



On Feb 28, 2022, at 09:36 , Bob Sneidar via use-livecode 
 wrote:

It occurs to me that this may drive a lot of hobbyist Livecoders away, and 
discourage others from coming onboard. There ought to be some kind of 
disclaimer on the website, since it is a paid product only now. I'd be a bit 
miffed if I bought an application for developing new apps and didn't know that 
there would be more cash outlay required before it would work.

Bob S



On Feb 28, 2022, at 09:25 , Paul Dupuis via use-livecode 
 wrote:

No, you really have to go through all of that. The few helper stacks out there 
are just front ends (using the shell command to call command line utilities 
from xcode) that make it easier once you have everything set up.

Yes, it sucks.


On 2/28/2022 12:18 PM, Bob Sneidar via use-livecode wrote:

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


___
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

Re: Into the future

[Klaus major-k via use-livecode]

Hi Bob,

> Am 28.02.2022 um 18:18 schrieb Bob Sneidar via use-livecode 
> :
> 
> 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

Re: Into the future

[Bob Sneidar via use-livecode]

I understand that perfectly. I am not blaming the LC people, but the net effect 
is what it is. I *would* like to see the option for NOT codesigning apps, so 
that the choice can be left up to us, but I suspect that with OS 11, the option 
to run non-codesigned apps has already been deprecated. 

Bob S


> On Feb 28, 2022, at 09:51 , Paul Dupuis via use-livecode 
>  wrote:
> 
> It isn't really a LiveCode ting. This is Apple placing these requirements on 
> their developers no matter what language you write code in for the macOS.
> 
> On 2/28/2022 12:43 PM, Bob Sneidar via use-livecode wrote:
>> I guess the question now becomes, what is the last Livecode app that can 
>> create standalones without requiring these certificates? I may need to plant 
>> my flag there and go no further.
>> 
>> Bob S
>> 
>> 
>>> On Feb 28, 2022, at 09:36 , Bob Sneidar via use-livecode 
>>>  wrote:
>>> 
>>> It occurs to me that this may drive a lot of hobbyist Livecoders away, and 
>>> discourage others from coming onboard. There ought to be some kind of 
>>> disclaimer on the website, since it is a paid product only now. I'd be a 
>>> bit miffed if I bought an application for developing new apps and didn't 
>>> know that there would be more cash outlay required before it would work.
>>> 
>>> Bob S
>>> 
>>> 
 On Feb 28, 2022, at 09:25 , Paul Dupuis via use-livecode 
  wrote:
 
 No, you really have to go through all of that. The few helper stacks out 
 there are just front ends (using the shell command to call command line 
 utilities from xcode) that make it easier once you have everything set up.
 
 Yes, it sucks.
 
 
 On 2/28/2022 12:18 PM, Bob Sneidar via use-livecode wrote:
> 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
> 
> 
> ___
> 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

Re: Into the future

[J. Landman Gay via use-livecode]

Since the app is only for internal use, you might be able to use the bypass 
that opens an unnotarized app. You'd need to give directions to the users.


https://support.apple.com/en-us/HT202491

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On February 28, 2022 11:45:29 AM Bob Sneidar via use-livecode 
 wrote:


I guess the question now becomes, what is the last Livecode app that can 
create standalones without requiring these certificates? I may need to 
plant my flag there and go no further.


Bob S


On Feb 28, 2022, at 09:36 , Bob Sneidar via use-livecode 
 wrote:


It occurs to me that this may drive a lot of hobbyist Livecoders away, and 
discourage others from coming onboard. There ought to be some kind of 
disclaimer on the website, since it is a paid product only now. I'd be a 
bit miffed if I bought an application for developing new apps and didn't 
know that there would be more cash outlay required before it would work.


Bob S


On Feb 28, 2022, at 09:25 , Paul Dupuis via use-livecode 
 wrote:


No, you really have to go through all of that. The few helper stacks out 
there are just front ends (using the shell command to call command line 
utilities from xcode) that make it easier once you have everything set up.


Yes, it sucks.


On 2/28/2022 12:18 PM, Bob Sneidar via use-livecode wrote:
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


___
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

Re: Into the future

[General 2018 via use-livecode]

Just had the same pain.

mrSignNotarizeHelperV3 was great and sorted all the MacOS command line stuff 
with ease ( I think LC should have this facility built into the standalone 
builder)

The Apple side of things unfortunately are what they are.

Regards
Camm

> On 28 Feb 2022, at 18:20, Bob Sneidar via use-livecode 
>  wrote:
> 
> I understand that perfectly. I am not blaming the LC people, but the net 
> effect is what it is. I *would* like to see the option for NOT codesigning 
> apps, so that the choice can be left up to us, but I suspect that with OS 11, 
> the option to run non-codesigned apps has already been deprecated. 
> 
> Bob S
> 
> 
>> On Feb 28, 2022, at 09:51 , Paul Dupuis via use-livecode 
>>  wrote:
>> 
>> It isn't really a LiveCode ting. This is Apple placing these requirements on 
>> their developers no matter what language you write code in for the macOS.
>> 
>>> On 2/28/2022 12:43 PM, Bob Sneidar via use-livecode wrote:
>>> I guess the question now becomes, what is the last Livecode app that can 
>>> create standalones without requiring these certificates? I may need to 
>>> plant my flag there and go no further.
>>> 
>>> Bob S
>>> 
>>> 
 On Feb 28, 2022, at 09:36 , Bob Sneidar via use-livecode 
  wrote:
 
 It occurs to me that this may drive a lot of hobbyist Livecoders away, and 
 discourage others from coming onboard. There ought to be some kind of 
 disclaimer on the website, since it is a paid product only now. I'd be a 
 bit miffed if I bought an application for developing new apps and didn't 
 know that there would be more cash outlay required before it would work.
 
 Bob S
 
 
> On Feb 28, 2022, at 09:25 , Paul Dupuis via use-livecode 
>  wrote:
> 
> No, you really have to go through all of that. The few helper stacks out 
> there are just front ends (using the shell command to call command line 
> utilities from xcode) that make it easier once you have everything set up.
> 
> Yes, it sucks.
> 
> 
> On 2/28/2022 12:18 PM, Bob Sneidar via use-livecode wrote:
>> 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
>> 
>> 
>> ___
>> 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, unsubscr

Re: Into the future

[J. Landman Gay via use-livecode]

Right. The blockage is in Gatekeeper, so any user running Mac Catalina or 
newer will get the warning regardless of how the app was created.


There's a way to download only the command line tools without needing to 
install Xcode. I wonder if that might work for you. I didn't save the info 
but someone here could probably tell you. Or you could search the list 
archives, I think it was Ralph DiMola who mentioned it.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On February 28, 2022 11:53:02 AM Paul Dupuis via use-livecode 
 wrote:



It isn't really a LiveCode ting. This is Apple placing these
requirements on their developers no matter what language you write code
in for the macOS.

On 2/28/2022 12:43 PM, Bob Sneidar via use-livecode wrote:
I guess the question now becomes, what is the last Livecode app that can 
create standalones without requiring these certificates? I may need to 
plant my flag there and go no further.


Bob S





___
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

Re: Into the future

[Dan Friedman via use-livecode]

" I think LC should have this facility built into the standalone builder "
Couldn't agree more!!   This should "just work" in LiveCode.

-Dan



On 2/28/22, 10:39 AM, "use-livecode on behalf of General 2018 via 
use-livecode"  wrote:

Just had the same pain.

mrSignNotarizeHelperV3 was great and sorted all the MacOS command line 
stuff with ease ( I think LC should have this facility built into the 
standalone builder)

The Apple side of things unfortunately are what they are.

Regards
Camm

> On 28 Feb 2022, at 18:20, Bob Sneidar via use-livecode 
 wrote:
> 
> I understand that perfectly. I am not blaming the LC people, but the net 
effect is what it is. I *would* like to see the option for NOT codesigning 
apps, so that the choice can be left up to us, but I suspect that with OS 11, 
the option to run non-codesigned apps has already been deprecated. 
> 
> Bob S
> 
> 
>> On Feb 28, 2022, at 09:51 , Paul Dupuis via use-livecode 
 wrote:
>> 
>> It isn't really a LiveCode ting. This is Apple placing these 
requirements on their developers no matter what language you write code in for 
the macOS.
>> 
>>> On 2/28/2022 12:43 PM, Bob Sneidar via use-livecode wrote:
>>> I guess the question now becomes, what is the last Livecode app that 
can create standalones without requiring these certificates? I may need to 
plant my flag there and go no further.
>>> 
>>> Bob S
>>> 
>>> 
 On Feb 28, 2022, at 09:36 , Bob Sneidar via use-livecode 
 wrote:
 
 It occurs to me that this may drive a lot of hobbyist Livecoders away, 
and discourage others from coming onboard. There ought to be some kind of 
disclaimer on the website, since it is a paid product only now. I'd be a bit 
miffed if I bought an application for developing new apps and didn't know that 
there would be more cash outlay required before it would work.
 
 Bob S
 
 
> On Feb 28, 2022, at 09:25 , Paul Dupuis via use-livecode 
 wrote:
> 
> No, you really have to go through all of that. The few helper stacks 
out there are just front ends (using the shell command to call command line 
utilities from xcode) that make it easier once you have everything set up.
> 
> Yes, it sucks.
> 
> 
> On 2/28/2022 12:18 PM, Bob Sneidar via use-livecode wrote:
>> 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
>> 
>> 
>> ___
>> 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 maili

Re: Into the future

[Bob Sneidar via use-livecode]

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 
>  wrote:
> 
> Hi Bob,
> 
>> Am 28.02.2022 um 18:18 schrieb Bob Sneidar via use-livecode 
>> :
>> 
>> 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

Re: Into the future

[Klaus major-k via use-livecode]

Hi Bob,

> Am 28.02.2022 um 19:52 schrieb Bob Sneidar via use-livecode 
> :
> 
> 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! 

I created a standalone with LC 9.6.6 without any certificate a couple of week 
ago!

> Bob S

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

Re: Into the future

[Klaus major-k via use-livecode]

Addendum

> Am 28.02.2022 um 19:52 schrieb Bob Sneidar via use-livecode 
> :
> 
> 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

I do not have Xcode installed just the neccessary command line tools via the 
TERMINAL, enter:
xcode-select --install

And it will download all neccessary tools.

--
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

Re: Into the future

[Sean Cole via use-livecode]

Klaus,

This is a fantastic shout out. Could you repost that on its own with a
better subject heading like "How to install XCode essentials only for
LiveCode builds" (or something better). It deserves not to get lost and
stand out in searches.

Nice one.

Sean Cole
*Pi Digital Productions Ltd*

On Mon, 28 Feb 2022 at 18:57, Klaus major-k via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Addendum
>
> > 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
>
> I do not have Xcode installed just the neccessary command line tools via
> the TERMINAL, enter:
> xcode-select --install
>
> And it will download all neccessary tools.
>
> --
> 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

Re: Into the future

[Roger Guay via use-livecode]

Hi Bob,

I just now created a mac standalone in Monterey and LC 9.9.6 without a hitch. I 
do have xCode installed but I don’t know if that makes the difference.

Roger

> On Feb 28, 2022, at 10:52 AM, Bob Sneidar via use-livecode 
>  wrote:
> 
> 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 
>>  wrote:
>> 
>> Hi Bob,
>> 
>>> Am 28.02.2022 um 18:18 schrieb Bob Sneidar via use-livecode 
>>> :
>>> 
>>> 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

Re: Into the future

[matthias rebbe via use-livecode]

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 
> :
> 
> 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 
>>  wrote:
>> 
>> Hi Bob,
>> 
>>> Am 28.02.2022 um 18:18 schrieb Bob Sneidar via use-livecode 
>>> :
>>> 
>>> 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

Re: Into the future

[Tom Glod via use-livecode]

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

Re: Into the future

[William Prothero via use-livecode]

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 
>  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

Re: Into the future

[Craig Newman via use-livecode]

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 
>  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 
>>  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 ur

Re: Into the future

[General 2018 via use-livecode]

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 
>  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 
>>  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 
  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
>

Re: Into the future

[Bob Sneidar via use-livecode]

I am getting, "Adding ad-hoc signature failed with error:  
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 /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 
>  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 
>>  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 
>>>  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 
>  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 standa

Re: Into the future

[Heather Laine via use-livecode]

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
 


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 
>  wrote:
> 
> I am getting, "Adding ad-hoc signature failed with error:  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  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 
>>  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 
>>>  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 
  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 
>>  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 stand

Re: Into the future

[Bob Sneidar via use-livecode]

Yup. I figured that out with the excellent help of the list users. :-)

Bob S


> On Mar 1, 2022, at 03:33 , Heather Laine via use-livecode 
>  wrote:
> 
> 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
>  
> 
> 
> Best Regards,
> 
> Heather
> 
> 
> Heather Laine
> Customer Services Manager
> LiveCode Ltd
> www.livecode.com


___
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