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 
> <use-livecode@lists.runrev.com>:
> 
> 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 
>> <use-livecode@lists.runrev.com <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 
>>> <use-livecode@lists.runrev.com>:
>>> 
>>> 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 
>>>>> <use-livecode@lists.runrev.com> 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 
>>>>> <use-livecode@lists.runrev.com>:
>>>>> 
>>>>> 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 
>>>>>>> <use-livecode@lists.runrev.com> 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 <mailto: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 
>> <http://lists.runrev.com/mailman/listinfo/use-livecode>
> _______________________________________________
> use-livecode mailing list
> use-livecode@lists.runrev.com <mailto: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 
> <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

Reply via email to