Hi Jim, Thanks for the ideas. I tried to codesign the file as part of the app’s signing process, but haven’t had any luck with that working. The alias idea is intriguing. I’m going to look into that.
Thanks. -- Cannon Smith Synergy Farm Solutions Inc. <[email protected]> <www.synergyfarmsolutions.com> > On Mar 7, 2020, at 8:17 AM, James Crate via 4D_Tech <[email protected]> > wrote: > > Will the other apps work if you create an alias in the Contents folder and > move the file to the Resources folder? I’m not sure how 4D’s commands work > with aliases, or whether aliases need to be signed. > >> So I’m wondering if there is a way to sign this file during the signing >> process. I’ve tried several variations of signing the file, but haven’t had >> any luck. I’m hoping someone knows of a way to sign a file like this so I >> don’t have to go down the difficult road of moving the file to another place. > > My impression based on nothing more than all sample signing code I’ve seen > has done it this way, is that all subdirectory items must be signed before > the app bundle. So if you have to force sign the file, you likely have to > resign the app. But, you probably wouldn’t have to re-sign all other > sub-items like plugins and other bundles. So after the app is built, you > could run a script that signs that file and the app again. So maybe > something like: ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
