Hi Erick and Jim,
Thanks for your thoughts. I’ve taken another approach which has solved most of
my issues. Instead of navigating the package and calling LEP commands myself on
each component, I’m now just using 4D’s SignApp.sh shell script. This handles
all the general cases just fine. I do have some executables that I keep in my
own resources folder which I sign manually (in code) before firing off 4D’s
shell script. So the process looks like this:
- Strip extended attributes and remove any code signing that exists anywhere in
the package
- Code sign the executables I keep in my Resources folder
- Call 4D’s SignApp.sh script (I’m using the one from 4D v18).
- Sent to Apple for notarization.
Doing this I’m now down to two errors:
issues": [
{
"severity": "error",
"code": null,
"path": "FFE5A08083D54FDE8D0FBAB1A1E06060.zip/Herdly
Team.app/Contents/Plugins/4D InternetCommands.bundle/Contents/MacOS/4D
InternetCommands",
"message": "The binary uses an SDK older than the 10.9 SDK.",
"docUrl": null,
"architecture": "i386"
},
{
"severity": "error",
"code": null,
"path": "FFE5A08083D54FDE8D0FBAB1A1E06060.zip/Herdly
Team.app/Contents/Plugins/cURL FTP.bundle/Contents/MacOS/cURL FTP",
"message": "The signature of the binary is invalid.",
"docUrl": null,
"architecture": "x86_64"
}
]
I’m not surprised at the Internet Commands one and was hoping I could use the
one from v18 which should overcome that. Haven’t tested that it works yet, but
it sounds like Jim already did that if I understood correctly. I’m less sure
what to do about the cURL FTP plugin. I know Miyako has it ready for
notarization and I assumed 4D’s shell script would take care of plugins
correctly, but maybe there is something I have to do manually with it.
Anyway, I’m much closer than I was yesterday. Thanks for everyone’s input.
--
Cannon Smith
Synergy Farm Solutions Inc.
<[email protected]>
<www.synergyfarmsolutions.com>
> On Feb 11, 2020, at 8:28 AM, ericklui678 via 4D_Tech <[email protected]>
> wrote:
>
> I was able to a notarize a v17 app yesterday by letting 4D handle the
> signing in the build application window with the "Sign application" option
> checked. This option will handle almost everything except the PHP libraries
> and InternetCommands.bundle (which can be substituted with the ones from
> v18). Try to avoid signing anything manually from terminal and let 4D handle
> the signing. This should cover the CodeEditor native component without
> issue.
**********************************************************************
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]
**********************************************************************
