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 v17. that is why I am now posting 2 builds, which are virtually identical except for the location of manifest.json. see: https://github.com/miyako/4d-plugin-curl-ftp/releases very curious to know if 3.9.v18 is successfully signed with the official shell script. On Feb 12, 2020, at 8:28, Cannon Smith via 4D_Tech <[email protected]<mailto:[email protected]>> wrote: 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. ********************************************************************** 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] **********************************************************************
