With 4D v17.3 HF3, I have errors like this:
{
"severity": "error",
"code": null,
"path": "Travel-1.0.7.app.zip/Travel.app/Contents/MacOS/Travel",
"message": "The executable does not have the hardened runtime enabled.",
"docUrl": null,
"architecture": "x86_64"
},
It might no longer be possible to notarize 4D apps until 4D enables the
hardened runtime for the 4D Runtime app as well as the 4D plugins.
I also had:
{
"severity": "error",
"code": null,
"path": "Travel-1.0.7.app.zip/Travel.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"
},
I don’t believe this app even uses 4D InternetCommands so I can probably just
remove that, unless the internal HTTP client commands like HTTP Get actually
call 4D InternetCommands.
As for the invalid signature bits, Apple recommends this command to help
diagnose notarization issues:
codesign -vvv --deep --strict $appPath
It spits out a list of things which are correctly signed, and says the
signature is valid. However, those are not the things listed in the
notarization log as having incorrect signatures. So codesign —deep is not
digging through all the subdirectories, just Contents/MacOS and
Contents/Frameworks. I’m going to test whether running codesign —deep on other
subdirectories containing binaries solves the signature issues.
Jim Crate
> On Feb 10, 2020, at 4:19 PM, Cannon Smith via 4D_Tech <[email protected]>
> wrote:
>
> Hi Everyone,
>
> A couple months ago I finally got my applications to notarize correctly. I’m
> in 4D v17.3 HF3, but using the PHP libraries from v18. As you probably know,
> Apple made changes last week and my notarization code has stopped working.
> Here is one example of the errors I’m getting back now:
>
> {
> "severity": "error",
> "code": null,
> "path": "B3A9E8C4BFA342E4B27E1E54538DEABA.zip/Herdly
> Team.app/Contents/Native
> Components/CodeEditor.bundle/Contents/MacOS/CodeEditor",
> "message": "The signature of the binary is invalid.",
> "docUrl": null,
> "architecture": "x86_64"
> },
>
> I have a log that spits out what is happening during signing. The relevant
> part is this:
>
>> codesign --verbose --timestamp --deep --sign Developer\ ID\ Application:\
>> Cannon\ Smith\ \(Y5RAH3A6C3\) /Users/Cannon/Library/Application\
>> Support/D9BE268668A4451A8FF411ADC94400CF/Standalone\ Build/Final\
>> Application/Herdly\ Team.app/Contents/Native\ Components/CodeEditor.bundle
>
> StdError: /Users/Cannon/Library/Application
> Support/D9BE268668A4451A8FF411ADC94400CF/Standalone Build/Final
> Application/Herdly Team.app/Contents/Native Components/CodeEditor.bundle:
> signed bundle with Mach-O thin (x86_64) [com.4d.component.CodeEditor]
>
>
> Further, both "codesign —verify --verbose” and "codesign -vvv —deep —strict”
> indicate that the app is signed correctly, but notarization returns errors
> like above.
>
> Does anyone know what I might be missing? This is very frustrating. :-(
>
> Thanks.
>
> --
> Cannon Smith
> Synergy Farm Solutions Inc.
> <[email protected]>
> <www.synergyfarmsolutions.com>
>
> **********************************************************************
> 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]
> **********************************************************************
**********************************************************************
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]
**********************************************************************
