Re: New Notarization Issues

Am 28.04.2020 um 17:01 schrieb Randy Jaynes via 4D_Tech <4d_tech@lists.4d.com>: > > I was cursing Apple frequently and for the first time in 20+ years (did I > really say that?) seriously considering becoming a Windows only programmer. I still develop on windows, but: Man am I happy that I

Re: New Notarization Issues

Jeremy, I won’t tell you how many day's worth of hours it took me to get my stuff through the process. I was cursing Apple frequently and for the first time in 20+ years (did I really say that?) seriously considering becoming a Windows only programmer. Randy

Re: New Notarization Issues

Randy and Spencer, Thanks. That’s exactly what I did and my application is now successfully notarized. I wish I understood what notarization actually involves. One day… Jeremy > On 28 Apr 2020, at 14:04, Randy Jaynes > wrote: > > For that one I was able to

Re: New Notarization Issues

For that one I was able to replace it with the php-fcgi-4d from the recent release of 4D v18. Randy -- Randy Jaynes Senior Programmer and Customer Support http://printpoint.com • 845.687.3741 • PrintPoint, Inc • 57 Ludlow Lane

Re: New Notarization Issues

Release notes for v17.4 indicate you can substitute PHP and Internet Commands from v18, or remove entirely: https://download.4d.com/Documents/Products_Documentation/LastVersions/Line_17/VIntl/PDF_Format/4D_v17_4_ReleaseNotes.pdf On 4/28/20, 4:33 AM, "4D_Tech on behalf of Jeremy Roussak via

Re: New Notarization Issues

Randy, thanks for that pointer and Miyako, thanks very much indeed, as ever, for that marvellous application. The huge slew of notarization errors has now been reduced to just one: "issues": [ { "severity": "error", "code": null, "path":

Re: New Notarization Issues

Jeremy, I would RUN to Miyako’s buildApp (https://github.com/miyako/4d-utility-build-application ) I found on the Catalina build machine that I’m using, I have to constantly sign the entire plugins folder. This database has been nothing

Re: New Notarization Issues

4Dv17R5, Mac Mojave An application which I have previously codesigned and successfully submitted for notarization is now failing to be notarized. The log file contains a stream of errors, complaining about 4D InternetCommands, InstallTool, Updater.app and others, the errors being invalid

Re: New Notarization Issues

I have successfully notarized my 4D app Using DropDMG. I’m using 4D v18.0 on MacOS Catalina. Paul Ringsmuth pringsm...@charter.net > On Apr 21, 2020, at 11:35 AM, Pat Bensky via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Peeps, > I ran into this problem also. I replaced the Internet

Re: New Notarization Issues

- check if software is signed codesign --verify --verbose {path} - check if software is notarised spctl --assess --verbose --type install {path} --- what you describe is normal behaviour for software that is not signed or notarised. https://support.apple.com/en-us/HT202491 > On Apr 22,

Re: New Notarization Issues

Peeps, I ran into this problem also. I replaced the Internet Commands plugin with the v18 version and that more or less fixed it. I say "more or less" because after downloading the installer (a .dmg created with DropDMG) and installing the app, the user gets the message *“CatBase 8.app” can’t be

Re: New Notarization Issues

code signature can easily get invalidated if the app or plugin was not packaged and distributed correctly. for example, if you simply sign, zip and upload a file to a public server, a downloaded copy would most probably be thrown to the bin. the developer should sign, archive (pkg, zip, dmg),

Re: New Notarization Issues

Hi Tim, Do you mean there is currently a way to use an offscreen web area (without creating an invisible form process), or is this something just happening internally? That would be really nice to have in order to take advantage of Javascript libraries. Thanks, John DeSoi, Ph.D. > On Feb

Re: New Notarization Issues

Hi Miyako, I have all my applications except one notarizing again since Apple’s recent changes. I appreciate you updating the cURL FTP and System Notification plugins. The application that isn’t notarizing has some other plugins that I’m hoping can be updated by their authors. I’m not sure

Re: New Notarization Issues

On Feb 12, 2020, at 11:35 AM, Timothy Penner via 4D_Tech <4d_tech@lists.4d.com> wrote: > > James et all, > > Please disregard my response from yesterday regarding removing the > WebViewerCEF.bundle as this was bad advice on my part! > > I have been informed that 4D is using the web area in

Re: New Notarization Issues

Hi Miyako, I just tried and 3.9.v18 is successfully signed with the official shell script. Thank you for the changes! I now have one application successfully notarizing again. Now I need to check my other applications to make sure they will still notarize. :-) -- Cannon Smith Synergy Farm

Re: New Notarization Issues

Hi Jim, Thanks. I’m now using the v18 Internet Commands and it is notarization correctly. -- Cannon Smith Synergy Farm Solutions Inc. > On Feb 11, 2020, at 5:40 PM, James Crate via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > I didn’t verify that the v18 4DIC is on a newer SDK, I replaced a

RE: New Notarization Issues

com> On Behalf Of James Crate via 4D_Tech Sent: Tuesday, February 11, 2020 1:26 PM To: 4D iNug Technical <4d_tech@lists.4d.com> Cc: James Crate Subject: Re: New Notarization Issues On Feb 11, 2020, at 2:58 PM, Timothy Penner via 4D_Tech <4d_tech@lists.4d.com> wrote: > > Regarding

Re: New Notarization Issues

if it works, then that's fine, but maybe there is a difference between Catalina 10.15.1 and 10.15.3. at least that has been my experience. On Feb 12, 2020, at 22:25, James Crate via 4D_Tech <4d_tech@lists.4d.com> wrote: plugin has manifest.json under Contents

Re: New Notarization Issues

On Feb 11, 2020, at 11:00 PM, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> wrote: > > I am not 100% sure, but it might be because plugins that support v17 (up to > R6) or earlier > have their manifest.json file under Contents, where the code sign CLI might > fail to find it. > > v18

Re: New Notarization Issues

Slightly related. Any idea why I have a plug-in that is signed but shows as damaged on Catalina but not in windows. I am not sure of other Mac OS versions. Chuck Sent from my iPhone > On Feb 11, 2020, at 8:01 PM, Keisuke Miyako via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > I am not 100%

Re: New Notarization Issues

I am not 100% sure, but it might be because plugins that support v17 (up to R6) or earlier have their manifest.json file under Contents, where the code sign CLI might fail to find it. v18 plugins have moved the location to Contents/Resources, but then, the plugin is no longer compatible with

Re: New Notarization Issues

On Feb 11, 2020, at 6:28 PM, Cannon Smith via 4D_Tech <4d_tech@lists.4d.com> wrote: > issues": [ >{ > "severity": "error", > "code": null, > "path": "FFE5A08083D54FDE8D0FBAB1A1E06060.zip/Herdly > Team.app/Contents/Plugins/4D InternetCommands.bundle/Contents/MacOS/4D >

Re: New Notarization Issues

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

Re: New Notarization Issues

On Feb 11, 2020, at 2:58 PM, Timothy Penner via 4D_Tech <4d_tech@lists.4d.com> wrote: > > Regarding this: >> However, after building I remove the “Contents/Native >> Components/WebViewerCEF.bundle”, which is an apparently unused 275MB >> package, so if I wanted to use the built-in signing, I’d

RE: New Notarization Issues

Crate via 4D_Tech Sent: Tuesday, February 11, 2020 11:44 AM To: 4D iNug Technical <4d_tech@lists.4d.com> Cc: James Crate Subject: Re: New Notarization Issues On Feb 11, 2020, at 10:58 AM, James Crate via 4D_Tech <4d_tech@lists.4d.com> wrote: > > With 4D v17.3 HF3, I have er

Re: New Notarization Issues

On Feb 11, 2020, at 10:58 AM, James Crate via 4D_Tech <4d_tech@lists.4d.com> wrote: > > 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

Re: New Notarization Issues

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":

Re: New Notarization Issues

Hi Cannon, 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