Notarizing question

[Phil]

Hi,

I had a quick google, and apparently the command:
"
Codesign -vvv <yourapp> will reveal the folder that it is rejecting.
"

should help you?

Seems an unwanted file has crept into the folder structure somewhere?

regards
Phil.

On 07/09/2020 09:09, Phil (OmnisList) via omnisdev-en wrote:
> Hi,
>
> We also use our own Icons, we named it ourselves as you can change the 
> name in the settings file, so removed the omnis.icns file...
>
> Had no issue as you describe it?
>
> regards
> Phil Potter
> Based in Chester in the UK.
>
> On 07/09/2020 07:12, Mike Matthews - Omnis wrote:
>> Odd that, We use a different Icon file as well, just a regular JPG 
>> converted to icns format.  Our fie is in the usual location, 
>> LinealSQLWorksDev v10.110.app/Contents/Resources/omnis.icns,
>>
>> We simply replace the existing omnis.icns file.
>>
>> Mike
>>
>>
>>
>> On 7 Sep 2020, at 02:17, Andy Hilton <  wrote:
>>
>> Ok, so utilizing the assistance from mike and Phil, I have got a 
>> little further…..
>>
>> The issue with the ‘Omnis’ file itself turned out to be a timing 
>> issue of when I was trying to sign it, so that appears to be ok now 
>> (signing it at the end of the signing list !)
>>
>> What I still have as an issue now though is a persistent : 'unsealed 
>> contents present in the bundle root’ error which is preventing 
>> further action - the Apple docs are less than helpful on what it may 
>> be - does anyone know any more about this one ?
>>
>> I have got an amended icns file involved - which some googling 
>> suggested may be an issue - however even exchanging that for the 
>> original omnis one didn’t change anything…..
>>
>>
>>
>>
>> On Sep 2, 2020, at 11:14 PM, Andy Hilton 
>> <andyh at totallybrilliant.com<mailto:andyh at totallybrilliant.com>> wrote:
>>
>> All
>>
>> I make my app, and follow the scripts I have previously got (an edit 
>> of Bas’s scripts) - and all passes muster, it appears notarized and 
>> stapled….
>>
>> I make a dmg - and again following the scripts I notarize my dmg
>>
>> Except this time I get a failure and following the logs, it tells me 
>> that the signature on the ‘Omnis’ app itself 
>> (TheApp/Contents/MacOS/Omnis) is invalid
>>
>> Anyone know why that may be and what command I should add to the 
>> prepare_build.sh script to correct it ?
>>
>> I am currently trying :
>>
>> codesign -f -o runtime --entitlements 
>> /Users/andy/Downloads/codesign/standard_entitlements.plist 
>> --timestamp --verbose -s "Developer ID Application: Andy Hilton 
>> (6UMDUSHJ58)" myAppName.app/Contents/MacOS/Omnis
>> codesign -f -o runtime --entitlements 
>> /Users/andy/Downloads/codesign/extended_entitlements.plist 
>> --timestamp --verbose -s "Developer ID Application: Andy Hilton 
>> (6UMDUSHJ58)" myAppName.app/Contents/MacOS/Omnis
>>
>>
>>
>> _____________________________________________________________
>> Manage your list subscriptions at http://lists.omnis-dev.com
>> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
>>
>> _____________________________________________________________
>> Manage your list subscriptions at 
>> http://lists.omnis-dev.com<http://lists.omnis-dev.com/>
>> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
>>
>> _____________________________________________________________
>> Manage your list subscriptions at http://lists.omnis-dev.com
>> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com 

-- 

P G Potter, 11 Regency Court, Mickle Trafford, Chester, UK.

This message is confidential and intended for the use only of the person 
to whom it is addressed. If you are not the intended recipient you are 
strictly prohibited from reading, disseminating, copying, printing, 
re-transmitting or using this message or its contents in any way. 
Opinions, conclusions and other information expressed in this message 
are not given or authorised by the Company unless otherwise indicated by 
an authorised representative independent of this message. The Company 
does not accept liability for any data corruption, interception or 
amendment to any e-mail or the consequences thereof. Emails addressed to 
individuals may not necessarily be read by that person unless they are 
in the office.