Re: Notarize Helper Stack in LC lesson updated

[General 2018 via use-livecode]

Hi Matthias,

Thanks for the reply.

Did not zip - I have now sent them zipped.

Built on = Mojave 10.14
Beta Tester = Monterey 12

Regards Camm

> On 29 Mar 2022, at 10:05, matthias rebbe via use-livecode 
>  wrote:
> 
> Matthias

___
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: Notarize Helper Stack in LC lesson updated

[matthias rebbe via use-livecode]

This could be of course a corrupted installer file. Did you resent him the 
file? 
Did you zip the .pgk before you've send it by email? If not, then try to send a 
zipped .pgk.

If you are sure, that the file is not corrupted, then ask your beta tester to 
try the following:
1. select the .pkg file
2. press CMD-i
3. change "open with" to use intaller.app.

On which macOS version did you create the installer .pkg and which macOS 
version is your beta tester using?


Matthias
> Am 29.03.2022 um 07:51 schrieb General 2018 via use-livecode 
> :
> 
> Used MrSign and made successful notarised .pkg
> 
> Works fine on my machine but when I emailed a beta tester the .pkg it showed 
> delevoper unidentifiable message and com.apple.installer.pagecontroller error 
> -1
> 
> Any idea ?
> 
> Regards
> Camm
> 
>> On 8 Feb 2022, at 23:48, matthias rebbe via use-livecode 
>> mailto:use-livecode@lists.runrev.com>> wrote:
>> 
>> Camm,
>> 
>> if i am not completely  wrong then this is a problem that can occur when you 
>> try the pkg installer on the same machine on which you've created it.
>> If the installer finds the same .app already somewhere on the hard disk it 
>> updates that app and does not install it into Applications folder.
>> 
>> So the best thing is to test the installer on an other machine. Or you could 
>> try the following:
>> After successful notarizing delete the app bundle of your standalone (you 
>> could make a zip file as backup first) and empty your trash. Make sure that 
>> there is no other copy of your .app even older ones. If there are others 
>> then delete them also and empty the trash.
>> 
>> Now try to run the .pkg installer. The app should now be installed in 
>> Applications folder.
>> 
>> Matthias
>> 
>> 
>>> Am 08.02.2022 um 22:23 schrieb General 2018 via use-livecode 
>>> :
>>> 
>>> Hi ,
>>> 
>>> Just a question on the .pkg install location.
>>> 
>>> When I execute the .pkg made by mrSign the installer completes okay but I 
>>> cannot find app ? not in /Applications or anywhere.
>>> 
>>> If I use 3rd party “Packages” to make a .pkg it’s installs app to 
>>> /Applications.
>>> 
>>> Any clue ? 
>>> 
>>> Regards Camm
>>> 
> On 3 Feb 2022, at 22:17, matthias rebbe via use-livecode 
> mailto:use-livecode@lists.runrev.com>> 
> wrote:
 
 Hi Camm,
 
 great to hear that you were able to successfully notarize.
 
 Regards,
 Matthias
 
 
> Am 03.02.2022 um 21:54 schrieb General 2018 via use-livecode 
> :
> 
> Update  Success.
> 
> Tried everything, then read a post that pointed to :-
> Apple Worldwide Developer Relations Certification Authority Cert
> Developer ID Certification Authority Cert
> 
> In Keychain my existing expired 2027, I downloaded and installed the 
> latest expiring 2030/2031 - re run mrSign and notarization success.
> 
> Status = Success 0 
> Status Code = Pac 
> Status Message = Age Approved
> 
> Regards
> Camm
> 
>>> On 29 Jan 2022, at 22:41, matthias rebbe via use-livecode 
>>>  wrote:
>> 
>> Hm, interesting. Seems to be a problem with a wrong or missing 
>> timestamp. So maybe adding --timestamp parameter will fix this.
>> 
>> Could you please change the following lines in the stack script of the 
>> NotarizeHelper stack and try again after that?
>> 
>> 
>> line 904
>> put "codesign --deep --force --verify --verbose --sign 
>> ##developerIDApplication## --options runtime  --entitlements 
>> ##entitlementsplist## ##myapp##" into tShell
>> with this line
>> put "codesign --timestamp --deep --force --verify --verbose --sign 
>> ##developerIDApplication## --options runtime  --entitlements 
>> ##entitlementsplist## ##myapp##" into tShell
>> 
>> 
>> 
>> line 908
>> put "codesign --deep --force --verify --verbose --sign 
>> ##developerIDApplication## --options runtime ##myapp##" into tShell
>> with
>> put "codesign --timestamp --deep --force --verify --verbose --sign 
>> ##developerIDApplication## --options runtime ##myapp##" into tShell
>> 
>> line 953
>> put "codesign --deep --force --verify --verbose --sign 
>> ##developerIDApplication## --options runtime ##myDMG##" into tShell
>> with
>> put "codesign --timestamp --deep --force --verify --verbose --sign 
>> ##developerIDApplication## --options runtime ##myDMG##" into tShell
>> 
>> 
>>> Am 29.01.2022 um 22:17 schrieb General 2018 via use-livecode 
>>> :
>>> 
>>> Tried all these, result the same.
>>> 
>>> In show “Notarization requests” for each :-
>>> 
>>> Status = invalid 2
>>> Status Code = Pac
>>> Status Message = age invalid
>>> 
>>> Regards Camm
>>> 
> On 29 Jan 2022, at 20:37, matthias rebbe via use-livecode 
>  wrote:
 
>>> ___

Re: Notarize Helper Stack in LC lesson updated

[General 2018 via use-livecode]

Used MrSign and made successful notarised .pkg

Works fine on my machine but when I emailed a beta tester the .pkg it showed 
delevoper unidentifiable message and com.apple.installer.pagecontroller error -1

Any idea ?

Regards
Camm

> On 8 Feb 2022, at 23:48, matthias rebbe via use-livecode 
>  wrote:
> 
> Camm,
> 
> if i am not completely  wrong then this is a problem that can occur when you 
> try the pkg installer on the same machine on which you've created it.
> If the installer finds the same .app already somewhere on the hard disk it 
> updates that app and does not install it into Applications folder.
> 
> So the best thing is to test the installer on an other machine. Or you could 
> try the following:
> After successful notarizing delete the app bundle of your standalone (you 
> could make a zip file as backup first) and empty your trash. Make sure that 
> there is no other copy of your .app even older ones. If there are others then 
> delete them also and empty the trash.
> 
> Now try to run the .pkg installer. The app should now be installed in 
> Applications folder.
> 
> Matthias
> 
> 
>> Am 08.02.2022 um 22:23 schrieb General 2018 via use-livecode 
>> :
>> 
>> Hi ,
>> 
>> Just a question on the .pkg install location.
>> 
>> When I execute the .pkg made by mrSign the installer completes okay but I 
>> cannot find app ? not in /Applications or anywhere.
>> 
>> If I use 3rd party “Packages” to make a .pkg it’s installs app to 
>> /Applications.
>> 
>> Any clue ? 
>> 
>> Regards Camm
>> 
 On 3 Feb 2022, at 22:17, matthias rebbe via use-livecode 
 mailto:use-livecode@lists.runrev.com>> 
 wrote:
>>> 
>>> Hi Camm,
>>> 
>>> great to hear that you were able to successfully notarize.
>>> 
>>> Regards,
>>> Matthias
>>> 
>>> 
 Am 03.02.2022 um 21:54 schrieb General 2018 via use-livecode 
 :
 
 Update  Success.
 
 Tried everything, then read a post that pointed to :-
 Apple Worldwide Developer Relations Certification Authority Cert
 Developer ID Certification Authority Cert
 
 In Keychain my existing expired 2027, I downloaded and installed the 
 latest expiring 2030/2031 - re run mrSign and notarization success.
 
 Status = Success 0 
 Status Code = Pac 
 Status Message = Age Approved
 
 Regards
 Camm
 
>> On 29 Jan 2022, at 22:41, matthias rebbe via use-livecode 
>>  wrote:
> 
> Hm, interesting. Seems to be a problem with a wrong or missing 
> timestamp. So maybe adding --timestamp parameter will fix this.
> 
> Could you please change the following lines in the stack script of the 
> NotarizeHelper stack and try again after that?
> 
> 
> line 904
> put "codesign --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime  --entitlements 
> ##entitlementsplist## ##myapp##" into tShell
> with this line
> put "codesign --timestamp --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime  --entitlements 
> ##entitlementsplist## ##myapp##" into tShell
> 
> 
> 
> line 908
> put "codesign --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime ##myapp##" into tShell
> with
> put "codesign --timestamp --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime ##myapp##" into tShell
> 
> line 953
> put "codesign --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime ##myDMG##" into tShell
> with
> put "codesign --timestamp --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime ##myDMG##" into tShell
> 
> 
>> Am 29.01.2022 um 22:17 schrieb General 2018 via use-livecode 
>> :
>> 
>> Tried all these, result the same.
>> 
>> In show “Notarization requests” for each :-
>> 
>> Status = invalid 2
>> Status Code = Pac
>> Status Message = age invalid
>> 
>> Regards Camm
>> 
 On 29 Jan 2022, at 20:37, matthias rebbe via use-livecode 
  wrote:
>>> 
>> ___
>> 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 
 

Re: Notarize Helper Stack in LC lesson updated

[General 2018 via use-livecode]

Hi ,

Yes, that was the issue - I was thinking the bundle ID could be the same for 
the product series and the version name and version number dictated the 
difference.

Once again thanks for the help on this.

Regards Camm

> On 10 Feb 2022, at 10:53, matthias rebbe via use-livecode 
>  wrote:
> 

___
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: Notarize Helper Stack in LC lesson updated

[matthias rebbe via use-livecode]

Hi Camm,

Could it be that both standalones have the same Bundle Identifier 
(NSBundleIdentifier). You can find the value in LC's standalone settings ->Mac 
at the bottom.
Seems that not the Bundle Name but the Bundle Identifier is responsible for 
that relocation behaviour.

More information could be found here
https://scriptingosx.com/2017/05/relocatable-package-installers-and-quickpkg-update/

Regards,
Matthias



> Am 09.02.2022 um 23:35 schrieb General 2018 via use-livecode 
> :
> 
> One more slight issue …
> 
> I have 2 apps with standalone CFBundleNames :-
> 
> Myapp 1.0.0 Free
> 
> Myapp 2.0.0
> 
> Though they have different CFBundleNames they will not install on the same 
> machine.
> Delete either and one installs fine to Applications.
> 
> Any CF settings conflict or still issue with above names ?
> 
> Regards Camm
> 
>> On 9 Feb 2022, at 21:56, General 2018 via use-livecode 
>>  wrote:
>> 
> ___
> 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: Notarize Helper Stack in LC lesson updated

[General 2018 via use-livecode]

One more slight issue …

I have 2 apps with standalone CFBundleNames :-

Myapp 1.0.0 Free

Myapp 2.0.0

Though they have different CFBundleNames they will not install on the same 
machine.
Delete either and one installs fine to Applications.

Any CF settings conflict or still issue with above names ?

Regards Camm

> On 9 Feb 2022, at 21:56, General 2018 via use-livecode 
>  wrote:
> 
___
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: Notarize Helper Stack in LC lesson updated

[General 2018 via use-livecode]

Thanks for the tips.

Removed existing standalone’s etc and the .pkg installed nicely to the 
Applications folder.

Regards Camm

> On 9 Feb 2022, at 00:31, Matthias Rebbe via use-livecode 
>  wrote:
> 
> What i forgot.
> 
> You could open console.app and open the install log. There you could see 
> where the app was installed or better said which app was updated/overwritten.
> You should find an entry like this
> 
>PackageKit: Applications/MyTest.app relocated to ... 
> 
> 
> Just search for 'relocated' and you should see what happened.
> 
> And please be aware. The app that is updated/overwritten is not determined by 
> the its file name, but by the bundle name (CFBundelName) you've entered in 
> the standalone settings.
> 
> Let's say we have MyNewSampleApp.app and its CFBundleName is for example 
> 'MySampleApp' and we've created an pkg installer from it. And we have another 
> app on the hard disk named 'MyOldSampleApp' which also has the CFBundleName 
> 'MySampleApp'.
> If you then run the pkg installer then chances are high that the file 
> 'MyOldSampleApp' is overwritten instead of  a new file 'MyNewSampleApp.app' 
> is written into Applications folder.
> 
> There are ways to avoid this and tell the package installer to not relocate, 
> but therefore the pkg building command in mrNotarizeHelper stack had to be 
> adjusted. Unfortunately i have currently not enough time to dive into that.
> 
> 
> Regards,
> Matthias
> 
> 
> Von meinem iPhone gesendet
> 
>> Am 09.02.2022 um 00:48 schrieb matthias rebbe via use-livecode 
>> :
>> 
>> Camm,
>> 
>> if i am not completely  wrong then this is a problem that can occur when you 
>> try the pkg installer on the same machine on which you've created it.
>> If the installer finds the same .app already somewhere on the hard disk it 
>> updates that app and does not install it into Applications folder.
>> 
>> So the best thing is to test the installer on an other machine. Or you could 
>> try the following:
>> After successful notarizing delete the app bundle of your standalone (you 
>> could make a zip file as backup first) and empty your trash. Make sure that 
>> there is no other copy of your .app even older ones. If there are others 
>> then delete them also and empty the trash.
>> 
>> Now try to run the .pkg installer. The app should now be installed in 
>> Applications folder.
> ___
> 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: Notarize Helper Stack in LC lesson updated

[General 2018 via use-livecode]

Thanks - will have a look.

Regards Camm

> On 8 Feb 2022, at 22:29, Peter Bogdanoff via use-livecode 
>  wrote:
> 
> Hi Camm, 
> 
> I use mrSign all the time. The completed file is the same file you started 
> out with. The signing process makes modifications to the package and after 
> that, you can continue with making your installer with it, if that is your 
> final intention.
> 
> A warning, don’t test using that copy of the package, it will make a change 
> to the package making it invalid for future use.
> 
> Peter Bogdanoff
> 
>> On Feb 8, 2022, at 4:23 PM, General 2018 via use-livecode 
>>  wrote:
>> 
>> Hi ,
>> 
>> Just a question on the .pkg install location.
>> 
>> When I execute the .pkg made by mrSign the installer completes okay but I 
>> cannot find app ? not in /Applications or anywhere.
>> 
>> If I use 3rd party “Packages” to make a .pkg it’s installs app to 
>> /Applications.
>> 
>> Any clue ? 
>> 
>> Regards Camm
>> 
 On 3 Feb 2022, at 22:17, matthias rebbe via use-livecode 
  wrote:
>>> 
>>> Hi Camm,
>>> 
>>> great to hear that you were able to successfully notarize.
>>> 
>>> Regards,
>>> Matthias
>>> 
>>> 
 Am 03.02.2022 um 21:54 schrieb General 2018 via use-livecode 
 :
 
 Update  Success.
 
 Tried everything, then read a post that pointed to :-
 Apple Worldwide Developer Relations Certification Authority Cert
 Developer ID Certification Authority Cert
 
 In Keychain my existing expired 2027, I downloaded and installed the 
 latest expiring 2030/2031 - re run mrSign and notarization success.
 
 Status = Success 0 
 Status Code = Pac 
 Status Message = Age Approved
 
 Regards
 Camm
 
>> On 29 Jan 2022, at 22:41, matthias rebbe via use-livecode 
>>  wrote:
> 
> Hm, interesting. Seems to be a problem with a wrong or missing 
> timestamp. So maybe adding --timestamp parameter will fix this.
> 
> Could you please change the following lines in the stack script of the 
> NotarizeHelper stack and try again after that?
> 
> 
> line 904
> put "codesign --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime  --entitlements 
> ##entitlementsplist## ##myapp##" into tShell
> with this line
> put "codesign --timestamp --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime  --entitlements 
> ##entitlementsplist## ##myapp##" into tShell
> 
> 
> 
> line 908
> put "codesign --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime ##myapp##" into tShell
> with
> put "codesign --timestamp --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime ##myapp##" into tShell
> 
> line 953
> put "codesign --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime ##myDMG##" into tShell
> with
> put "codesign --timestamp --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime ##myDMG##" into tShell
> 
> 
>> Am 29.01.2022 um 22:17 schrieb General 2018 via use-livecode 
>> :
>> 
>> Tried all these, result the same.
>> 
>> In show “Notarization requests” for each :-
>> 
>> Status = invalid 2
>> Status Code = Pac
>> Status Message = age invalid
>> 
>> Regards Camm
>> 
 On 29 Jan 2022, at 20:37, matthias rebbe via use-livecode 
  wrote:
>>> 
>> ___
>> 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:
>> 

Re: Notarize Helper Stack in LC lesson updated

[General 2018 via use-livecode]

Thanks - will try these and report back.

Regards Camm

> On 9 Feb 2022, at 00:31, Matthias Rebbe via use-livecode 
>  wrote:
> 
> What i forgot.
> 
> You could open console.app and open the install log. There you could see 
> where the app was installed or better said which app was updated/overwritten.
> You should find an entry like this
> 
>PackageKit: Applications/MyTest.app relocated to ... 
> 
> 
> Just search for 'relocated' and you should see what happened.
> 
> And please be aware. The app that is updated/overwritten is not determined by 
> the its file name, but by the bundle name (CFBundelName) you've entered in 
> the standalone settings.
> 
> Let's say we have MyNewSampleApp.app and its CFBundleName is for example 
> 'MySampleApp' and we've created an pkg installer from it. And we have another 
> app on the hard disk named 'MyOldSampleApp' which also has the CFBundleName 
> 'MySampleApp'.
> If you then run the pkg installer then chances are high that the file 
> 'MyOldSampleApp' is overwritten instead of  a new file 'MyNewSampleApp.app' 
> is written into Applications folder.
> 
> There are ways to avoid this and tell the package installer to not relocate, 
> but therefore the pkg building command in mrNotarizeHelper stack had to be 
> adjusted. Unfortunately i have currently not enough time to dive into that.
> 
> 
> Regards,
> Matthias
> 
> 
> Von meinem iPhone gesendet
> 
>> Am 09.02.2022 um 00:48 schrieb matthias rebbe via use-livecode 
>> :
>> 
>> Camm,
>> 
>> if i am not completely  wrong then this is a problem that can occur when you 
>> try the pkg installer on the same machine on which you've created it.
>> If the installer finds the same .app already somewhere on the hard disk it 
>> updates that app and does not install it into Applications folder.
>> 
>> So the best thing is to test the installer on an other machine. Or you could 
>> try the following:
>> After successful notarizing delete the app bundle of your standalone (you 
>> could make a zip file as backup first) and empty your trash. Make sure that 
>> there is no other copy of your .app even older ones. If there are others 
>> then delete them also and empty the trash.
>> 
>> Now try to run the .pkg installer. The app should now be installed in 
>> Applications folder.
> ___
> 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: Notarize Helper Stack in LC lesson updated

[Matthias Rebbe via use-livecode]

What i forgot.

You could open console.app and open the install log. There you could see where 
the app was installed or better said which app was updated/overwritten.
You should find an entry like this

PackageKit: Applications/MyTest.app relocated to 
... 

Just search for 'relocated' and you should see what happened.

And please be aware. The app that is updated/overwritten is not determined by 
the its file name, but by the bundle name (CFBundelName) you've entered in the 
standalone settings.

Let's say we have MyNewSampleApp.app and its CFBundleName is for example 
'MySampleApp' and we've created an pkg installer from it. And we have another 
app on the hard disk named 'MyOldSampleApp' which also has the CFBundleName 
'MySampleApp'.
If you then run the pkg installer then chances are high that the file 
'MyOldSampleApp' is overwritten instead of  a new file 'MyNewSampleApp.app' is 
written into Applications folder.

There are ways to avoid this and tell the package installer to not relocate, 
but therefore the pkg building command in mrNotarizeHelper stack had to be 
adjusted. Unfortunately i have currently not enough time to dive into that.


Regards,
Matthias


Von meinem iPhone gesendet

> Am 09.02.2022 um 00:48 schrieb matthias rebbe via use-livecode 
> :
> 
> Camm,
> 
> if i am not completely  wrong then this is a problem that can occur when you 
> try the pkg installer on the same machine on which you've created it.
> If the installer finds the same .app already somewhere on the hard disk it 
> updates that app and does not install it into Applications folder.
> 
> So the best thing is to test the installer on an other machine. Or you could 
> try the following:
> After successful notarizing delete the app bundle of your standalone (you 
> could make a zip file as backup first) and empty your trash. Make sure that 
> there is no other copy of your .app even older ones. If there are others then 
> delete them also and empty the trash.
> 
> Now try to run the .pkg installer. The app should now be installed in 
> Applications folder.
___
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: Notarize Helper Stack in LC lesson updated

[matthias rebbe via use-livecode]

Camm,

if i am not completely  wrong then this is a problem that can occur when you 
try the pkg installer on the same machine on which you've created it.
If the installer finds the same .app already somewhere on the hard disk it 
updates that app and does not install it into Applications folder.

So the best thing is to test the installer on an other machine. Or you could 
try the following:
After successful notarizing delete the app bundle of your standalone (you could 
make a zip file as backup first) and empty your trash. Make sure that there is 
no other copy of your .app even older ones. If there are others then delete 
them also and empty the trash.

Now try to run the .pkg installer. The app should now be installed in 
Applications folder.

Matthias


> Am 08.02.2022 um 22:23 schrieb General 2018 via use-livecode 
> :
> 
> Hi ,
> 
> Just a question on the .pkg install location.
> 
> When I execute the .pkg made by mrSign the installer completes okay but I 
> cannot find app ? not in /Applications or anywhere.
> 
> If I use 3rd party “Packages” to make a .pkg it’s installs app to 
> /Applications.
> 
> Any clue ? 
> 
> Regards Camm
> 
>> On 3 Feb 2022, at 22:17, matthias rebbe via use-livecode 
>> mailto:use-livecode@lists.runrev.com>> wrote:
>> 
>> Hi Camm,
>> 
>> great to hear that you were able to successfully notarize.
>> 
>> Regards,
>> Matthias
>> 
>> 
>>> Am 03.02.2022 um 21:54 schrieb General 2018 via use-livecode 
>>> :
>>> 
>>> Update  Success.
>>> 
>>> Tried everything, then read a post that pointed to :-
>>> Apple Worldwide Developer Relations Certification Authority Cert
>>> Developer ID Certification Authority Cert
>>> 
>>> In Keychain my existing expired 2027, I downloaded and installed the latest 
>>> expiring 2030/2031 - re run mrSign and notarization success.
>>> 
>>> Status = Success 0 
>>> Status Code = Pac 
>>> Status Message = Age Approved
>>> 
>>> Regards
>>> Camm
>>> 
> On 29 Jan 2022, at 22:41, matthias rebbe via use-livecode 
>  wrote:
 
 Hm, interesting. Seems to be a problem with a wrong or missing timestamp. 
 So maybe adding --timestamp parameter will fix this.
 
 Could you please change the following lines in the stack script of the 
 NotarizeHelper stack and try again after that?
 
 
 line 904
 put "codesign --deep --force --verify --verbose --sign 
 ##developerIDApplication## --options runtime  --entitlements 
 ##entitlementsplist## ##myapp##" into tShell
 with this line
 put "codesign --timestamp --deep --force --verify --verbose --sign 
 ##developerIDApplication## --options runtime  --entitlements 
 ##entitlementsplist## ##myapp##" into tShell
 
 
 
 line 908
 put "codesign --deep --force --verify --verbose --sign 
 ##developerIDApplication## --options runtime ##myapp##" into tShell
 with
 put "codesign --timestamp --deep --force --verify --verbose --sign 
 ##developerIDApplication## --options runtime ##myapp##" into tShell
 
 line 953
 put "codesign --deep --force --verify --verbose --sign 
 ##developerIDApplication## --options runtime ##myDMG##" into tShell
 with
 put "codesign --timestamp --deep --force --verify --verbose --sign 
 ##developerIDApplication## --options runtime ##myDMG##" into tShell
 
 
> Am 29.01.2022 um 22:17 schrieb General 2018 via use-livecode 
> :
> 
> Tried all these, result the same.
> 
> In show “Notarization requests” for each :-
> 
> Status = invalid 2
> Status Code = Pac
> Status Message = age invalid
> 
> Regards Camm
> 
>>> On 29 Jan 2022, at 20:37, matthias rebbe via use-livecode 
>>>  wrote:
>> 
> ___
> 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: Notarize Helper Stack in LC lesson updated

[Peter Bogdanoff via use-livecode]

Hi Camm, 

I use mrSign all the time. The completed file is the same file you started out 
with. The signing process makes modifications to the package and after that, 
you can continue with making your installer with it, if that is your final 
intention.

A warning, don’t test using that copy of the package, it will make a change to 
the package making it invalid for future use.

Peter Bogdanoff

> On Feb 8, 2022, at 4:23 PM, General 2018 via use-livecode 
>  wrote:
> 
> Hi ,
> 
> Just a question on the .pkg install location.
> 
> When I execute the .pkg made by mrSign the installer completes okay but I 
> cannot find app ? not in /Applications or anywhere.
> 
> If I use 3rd party “Packages” to make a .pkg it’s installs app to 
> /Applications.
> 
> Any clue ? 
> 
> Regards Camm
> 
>> On 3 Feb 2022, at 22:17, matthias rebbe via use-livecode 
>>  wrote:
>> 
>> Hi Camm,
>> 
>> great to hear that you were able to successfully notarize.
>> 
>> Regards,
>> Matthias
>> 
>> 
>>> Am 03.02.2022 um 21:54 schrieb General 2018 via use-livecode 
>>> :
>>> 
>>> Update  Success.
>>> 
>>> Tried everything, then read a post that pointed to :-
>>> Apple Worldwide Developer Relations Certification Authority Cert
>>> Developer ID Certification Authority Cert
>>> 
>>> In Keychain my existing expired 2027, I downloaded and installed the latest 
>>> expiring 2030/2031 - re run mrSign and notarization success.
>>> 
>>> Status = Success 0 
>>> Status Code = Pac 
>>> Status Message = Age Approved
>>> 
>>> Regards
>>> Camm
>>> 
> On 29 Jan 2022, at 22:41, matthias rebbe via use-livecode 
>  wrote:
 
 Hm, interesting. Seems to be a problem with a wrong or missing timestamp. 
 So maybe adding --timestamp parameter will fix this.
 
 Could you please change the following lines in the stack script of the 
 NotarizeHelper stack and try again after that?
 
 
 line 904
 put "codesign --deep --force --verify --verbose --sign 
 ##developerIDApplication## --options runtime  --entitlements 
 ##entitlementsplist## ##myapp##" into tShell
 with this line
 put "codesign --timestamp --deep --force --verify --verbose --sign 
 ##developerIDApplication## --options runtime  --entitlements 
 ##entitlementsplist## ##myapp##" into tShell
 
 
 
 line 908
 put "codesign --deep --force --verify --verbose --sign 
 ##developerIDApplication## --options runtime ##myapp##" into tShell
 with
 put "codesign --timestamp --deep --force --verify --verbose --sign 
 ##developerIDApplication## --options runtime ##myapp##" into tShell
 
 line 953
 put "codesign --deep --force --verify --verbose --sign 
 ##developerIDApplication## --options runtime ##myDMG##" into tShell
 with
 put "codesign --timestamp --deep --force --verify --verbose --sign 
 ##developerIDApplication## --options runtime ##myDMG##" into tShell
 
 
> Am 29.01.2022 um 22:17 schrieb General 2018 via use-livecode 
> :
> 
> Tried all these, result the same.
> 
> In show “Notarization requests” for each :-
> 
> Status = invalid 2
> Status Code = Pac
> Status Message = age invalid
> 
> Regards Camm
> 
>>> On 29 Jan 2022, at 20:37, matthias rebbe via use-livecode 
>>>  wrote:
>> 
> ___
> 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: Notarize Helper Stack in LC lesson updated

[General 2018 via use-livecode]

Hi ,

Just a question on the .pkg install location.

When I execute the .pkg made by mrSign the installer completes okay but I 
cannot find app ? not in /Applications or anywhere.

If I use 3rd party “Packages” to make a .pkg it’s installs app to /Applications.

Any clue ? 

Regards Camm

> On 3 Feb 2022, at 22:17, matthias rebbe via use-livecode 
>  wrote:
> 
> Hi Camm,
> 
> great to hear that you were able to successfully notarize.
> 
> Regards,
> Matthias
> 
> 
>> Am 03.02.2022 um 21:54 schrieb General 2018 via use-livecode 
>> :
>> 
>> Update  Success.
>> 
>> Tried everything, then read a post that pointed to :-
>> Apple Worldwide Developer Relations Certification Authority Cert
>> Developer ID Certification Authority Cert
>> 
>> In Keychain my existing expired 2027, I downloaded and installed the latest 
>> expiring 2030/2031 - re run mrSign and notarization success.
>> 
>> Status = Success 0 
>> Status Code = Pac 
>> Status Message = Age Approved
>> 
>> Regards
>> Camm
>> 
 On 29 Jan 2022, at 22:41, matthias rebbe via use-livecode 
  wrote:
>>> 
>>> Hm, interesting. Seems to be a problem with a wrong or missing timestamp. 
>>> So maybe adding --timestamp parameter will fix this.
>>> 
>>> Could you please change the following lines in the stack script of the 
>>> NotarizeHelper stack and try again after that?
>>> 
>>> 
>>> line 904
>>> put "codesign --deep --force --verify --verbose --sign 
>>> ##developerIDApplication## --options runtime  --entitlements 
>>> ##entitlementsplist## ##myapp##" into tShell
>>> with this line
>>> put "codesign --timestamp --deep --force --verify --verbose --sign 
>>> ##developerIDApplication## --options runtime  --entitlements 
>>> ##entitlementsplist## ##myapp##" into tShell
>>> 
>>> 
>>> 
>>> line 908
>>> put "codesign --deep --force --verify --verbose --sign 
>>> ##developerIDApplication## --options runtime ##myapp##" into tShell
>>> with
>>> put "codesign --timestamp --deep --force --verify --verbose --sign 
>>> ##developerIDApplication## --options runtime ##myapp##" into tShell
>>> 
>>> line 953
>>> put "codesign --deep --force --verify --verbose --sign 
>>> ##developerIDApplication## --options runtime ##myDMG##" into tShell
>>> with
>>> put "codesign --timestamp --deep --force --verify --verbose --sign 
>>> ##developerIDApplication## --options runtime ##myDMG##" into tShell
>>> 
>>> 
 Am 29.01.2022 um 22:17 schrieb General 2018 via use-livecode 
 :
 
 Tried all these, result the same.
 
 In show “Notarization requests” for each :-
 
 Status = invalid 2
 Status Code = Pac
 Status Message = age invalid
 
 Regards Camm
 
>> On 29 Jan 2022, at 20:37, matthias rebbe via use-livecode 
>>  wrote:
> 
 ___
 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: Notarize Helper Stack in LC lesson updated

[matthias rebbe via use-livecode]

Hi Camm,

great to hear that you were able to successfully notarize.

Regards,
Matthias


> Am 03.02.2022 um 21:54 schrieb General 2018 via use-livecode 
> :
> 
> Update  Success.
> 
> Tried everything, then read a post that pointed to :-
> Apple Worldwide Developer Relations Certification Authority Cert
> Developer ID Certification Authority Cert
> 
> In Keychain my existing expired 2027, I downloaded and installed the latest 
> expiring 2030/2031 - re run mrSign and notarization success.
> 
> Status = Success 0 
> Status Code = Pac 
> Status Message = Age Approved
> 
> Regards
> Camm
> 
>> On 29 Jan 2022, at 22:41, matthias rebbe via use-livecode 
>>  wrote:
>> 
>> Hm, interesting. Seems to be a problem with a wrong or missing timestamp. 
>> So maybe adding --timestamp parameter will fix this.
>> 
>> Could you please change the following lines in the stack script of the 
>> NotarizeHelper stack and try again after that?
>> 
>> 
>> line 904
>> put "codesign --deep --force --verify --verbose --sign 
>> ##developerIDApplication## --options runtime  --entitlements 
>> ##entitlementsplist## ##myapp##" into tShell
>> with this line
>> put "codesign --timestamp --deep --force --verify --verbose --sign 
>> ##developerIDApplication## --options runtime  --entitlements 
>> ##entitlementsplist## ##myapp##" into tShell
>> 
>> 
>> 
>> line 908
>> put "codesign --deep --force --verify --verbose --sign 
>> ##developerIDApplication## --options runtime ##myapp##" into tShell
>> with
>> put "codesign --timestamp --deep --force --verify --verbose --sign 
>> ##developerIDApplication## --options runtime ##myapp##" into tShell
>> 
>> line 953
>> put "codesign --deep --force --verify --verbose --sign 
>> ##developerIDApplication## --options runtime ##myDMG##" into tShell
>> with
>> put "codesign --timestamp --deep --force --verify --verbose --sign 
>> ##developerIDApplication## --options runtime ##myDMG##" into tShell
>> 
>> 
>>> Am 29.01.2022 um 22:17 schrieb General 2018 via use-livecode 
>>> :
>>> 
>>> Tried all these, result the same.
>>> 
>>> In show “Notarization requests” for each :-
>>> 
>>> Status = invalid 2
>>> Status Code = Pac
>>> Status Message = age invalid
>>> 
>>> Regards Camm
>>> 
> On 29 Jan 2022, at 20:37, matthias rebbe via use-livecode 
>  wrote:
 
>>> ___
>>> 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: Notarize Helper Stack in LC lesson updated

[General 2018 via use-livecode]

Update  Success.

Tried everything, then read a post that pointed to :-
Apple Worldwide Developer Relations Certification Authority Cert
Developer ID Certification Authority Cert

In Keychain my existing expired 2027, I downloaded and installed the latest 
expiring 2030/2031 - re run mrSign and notarization success.

Status = Success 0 
Status Code = Pac 
Status Message = Age Approved

Regards
Camm

> On 29 Jan 2022, at 22:41, matthias rebbe via use-livecode 
>  wrote:
> 
> Hm, interesting. Seems to be a problem with a wrong or missing timestamp. So 
> maybe adding --timestamp parameter will fix this.
> 
> Could you please change the following lines in the stack script of the 
> NotarizeHelper stack and try again after that?
> 
> 
> line 904
> put "codesign --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime  --entitlements 
> ##entitlementsplist## ##myapp##" into tShell
> with this line
> put "codesign --timestamp --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime  --entitlements 
> ##entitlementsplist## ##myapp##" into tShell
> 
> 
> 
> line 908
> put "codesign --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime ##myapp##" into tShell
> with
> put "codesign --timestamp --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime ##myapp##" into tShell
> 
> line 953
> put "codesign --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime ##myDMG##" into tShell
> with
> put "codesign --timestamp --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime ##myDMG##" into tShell
> 
> 
>> Am 29.01.2022 um 22:17 schrieb General 2018 via use-livecode 
>> :
>> 
>> Tried all these, result the same.
>> 
>> In show “Notarization requests” for each :-
>> 
>> Status = invalid 2
>> Status Code = Pac
>> Status Message = age invalid
>> 
>> Regards Camm
>> 
 On 29 Jan 2022, at 20:37, matthias rebbe via use-livecode 
  wrote:
>>> 
>> ___
>> 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: Notarize Helper Stack in LC lesson updated

[General 2018 via use-livecode]

Tried those with each of the previous suggests still the same error.

Maybe I have missed something in the setup ? Will check everything again.

Regards Camm

> On 29 Jan 2022, at 22:41, matthias rebbe via use-livecode 
>  wrote:
> 
> Hm, interesting. Seems to be a problem with a wrong or missing timestamp. So 
> maybe adding --timestamp parameter will fix this.
> 
> Could you please change the following lines in the stack script of the 
> NotarizeHelper stack and try again after that?
> 
> 
> line 904
> put "codesign --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime  --entitlements 
> ##entitlementsplist## ##myapp##" into tShell
> with this line
> put "codesign --timestamp --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime  --entitlements 
> ##entitlementsplist## ##myapp##" into tShell
> 
> 
> 
> line 908
> put "codesign --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime ##myapp##" into tShell
> with
> put "codesign --timestamp --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime ##myapp##" into tShell
> 
> line 953
> put "codesign --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime ##myDMG##" into tShell
> with
> put "codesign --timestamp --deep --force --verify --verbose --sign 
> ##developerIDApplication## --options runtime ##myDMG##" into tShell
> 
> 
>> Am 29.01.2022 um 22:17 schrieb General 2018 via use-livecode 
>> :
>> 
>> Tried all these, result the same.
>> 
>> In show “Notarization requests” for each :-
>> 
>> Status = invalid 2
>> Status Code = Pac
>> Status Message = age invalid
>> 
>> Regards Camm
>> 
 On 29 Jan 2022, at 20:37, matthias rebbe via use-livecode 
  wrote:
>>> 
>> ___
>> 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: Notarize Helper Stack in LC lesson updated

[matthias rebbe via use-livecode]

Hm, interesting. Seems to be a problem with a wrong or missing timestamp. So 
maybe adding --timestamp parameter will fix this.

Could you please change the following lines in the stack script of the 
NotarizeHelper stack and try again after that?


line 904
put "codesign --deep --force --verify --verbose --sign 
##developerIDApplication## --options runtime  --entitlements 
##entitlementsplist## ##myapp##" into tShell
with this line
put "codesign --timestamp --deep --force --verify --verbose --sign 
##developerIDApplication## --options runtime  --entitlements 
##entitlementsplist## ##myapp##" into tShell



line 908
put "codesign --deep --force --verify --verbose --sign 
##developerIDApplication## --options runtime ##myapp##" into tShell
with
put "codesign --timestamp --deep --force --verify --verbose --sign 
##developerIDApplication## --options runtime ##myapp##" into tShell

line 953
put "codesign --deep --force --verify --verbose --sign 
##developerIDApplication## --options runtime ##myDMG##" into tShell
with
put "codesign --timestamp --deep --force --verify --verbose --sign 
##developerIDApplication## --options runtime ##myDMG##" into tShell


> Am 29.01.2022 um 22:17 schrieb General 2018 via use-livecode 
> :
> 
> Tried all these, result the same.
> 
> In show “Notarization requests” for each :-
> 
> Status = invalid 2
> Status Code = Pac
> Status Message = age invalid
> 
> Regards Camm
> 
>> On 29 Jan 2022, at 20:37, matthias rebbe via use-livecode 
>>  wrote:
>> 
> ___
> 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: Notarize Helper Stack in LC lesson updated

[General 2018 via use-livecode]

Tried all these, result the same.

In show “Notarization requests” for each :-

Status = invalid 2
Status Code = Pac
Status Message = age invalid

Regards Camm

> On 29 Jan 2022, at 20:37, matthias rebbe via use-livecode 
>  wrote:
> 
___
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: Notarize Helper Stack in LC lesson updated

[General 2018 via use-livecode]

No added files.

Mojave 10.14.6

LC 9.6.6

Regards
Camm

> On 29 Jan 2022, at 20:20, matthias rebbe via use-livecode 
>  wrote:
> 

___
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: Notarize Helper Stack in LC lesson updated

[matthias rebbe via use-livecode]

Camm,

another thing you could try is to replace the line which creates the zip file.

In the stack script of the NotarizeHelper replace this line (line no. 1569)
put "zip -r ##zipfile## ##appbundle##" into tShell

with this one

put "zip -y -r ##zipfile## ##appbundle##" into tShell


or if that does not solve it, replace  the line with the following one and try 
again.

put "/usr/bin/ditto -c -k --sequesterRsrc --keepParent ##zipfile## 
##appbundle##" into tShell

Matthias



> Am 29.01.2022 um 21:19 schrieb matthias rebbe via use-livecode 
> :
> 
> 
> Did you add any files to the standalone (application bundle) after you've 
> created it with LC?
> In this thread https://developer.apple.com/forums/thread/116831 
>   someone points out that 
> this error can be caused when nested code is in a wrong location.
> 
> Look here for the part about nested code:
> https://developer.apple.com/library/archive/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG201
>  
> 
> 
> Btw. Which version of macOS are you using? And with which version of LC did 
> you build the standalone?
> 
> Regards,
> Matthias
> 
> 
> 
> 
> 
>> Am 29.01.2022 um 19:51 schrieb General 2018 via use-livecode 
>> :
>> 
>> signature of the binary is invalid”
> 
> ___
> 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: Notarize Helper Stack in LC lesson updated

[matthias rebbe via use-livecode]

Did you add any files to the standalone (application bundle) after you've 
created it with LC?
In this thread https://developer.apple.com/forums/thread/116831 
  someone points out that 
this error can be caused when nested code is in a wrong location.

Look here for the part about nested code:
https://developer.apple.com/library/archive/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG201
 


Btw. Which version of macOS are you using? And with which version of LC did you 
build the standalone?

Regards,
Matthias





> Am 29.01.2022 um 19:51 schrieb General 2018 via use-livecode 
> :
> 
> signature of the binary is invalid”

___
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: Notarize Helper Stack in LC lesson updated

[General 2018 via use-livecode]

Hi ,

Just seen this - fantastic help.

Just getting “signature of the binary is invalid” and “signature does not 
include secure time stamp” as reply following notarization attempt. Status Code 
2 Package Invalid.

Regards
Camm

> On 27 Jan 2022, at 22:54, matthias rebbe via use-livecode 
>  wrote:
> 
> For those who are interested, i've uploaded a new version of the Notarize 
> Helper stack to the Livecode lesson 
> https://lessons.livecode.com/m/4071/l/1122100-codesigning-and-notarizing-your-lc-standalone-for-distribution-outside-the-mac-appstore
> 
> The direct download link is 
> https://media.screensteps.com/attachment_assets/assets/005/023/860/original/mrSignNotarizeHelperV3.livecode
> 
> 
> Regards,
> Matthias
> ___
> 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: Notarize Helper Stack in LC lesson updated

[Tom Glod via use-livecode]

Thank you, I will be going through this tutorial next week.
Any help to make this easier is very much appreciated.

On Thu, Jan 27, 2022 at 5:54 PM matthias rebbe via use-livecode <
use-livecode@lists.runrev.com> wrote:

> For those who are interested, i've uploaded a new version of the Notarize
> Helper stack to the Livecode lesson
>
> https://lessons.livecode.com/m/4071/l/1122100-codesigning-and-notarizing-your-lc-standalone-for-distribution-outside-the-mac-appstore
>
> The direct download link is
>
> https://media.screensteps.com/attachment_assets/assets/005/023/860/original/mrSignNotarizeHelperV3.livecode
>
>
> Regards,
> Matthias
> ___
> 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