Hmm. Needless to say, I immediately solved part of the problem but not all.
Removing all the extended attributes on the huge number of files in the compiled application then allows code signing to work from the command line. The application seems to work OK, but I’m wondering why so many files, most of them from 4D, have attributes which prevent signing from working. Or maybe I’m just neurotic. Jeremy > On 14 Oct 2018, at 14:54, Jeremy Roussak via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > I have a “developer ID application” certificate from Apple, just created. It > shows in my keychain > (https://www.dropbox.com/s/wsyl0w7jjqmz0mw/Screenshot%202018-10-14%2014.51.21.jpg?dl=0 > > <https://www.dropbox.com/s/wsyl0w7jjqmz0mw/Screenshot%202018-10-14%2014.51.21.jpg?dl=0>). > > What do I put into the “Name of certificate” in the “Build application” > dialog? I’ve tried my name only, the parenthesised text only and both, but > each time I get “Code signature failed”. > > If I try the command line codesign in Terminal, I get "resource fork, Finder > information, or similar detritus not allowed”. > > I assume I’ve missed something. Any tips gratefully received. > > Jeremy > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.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:4d_tech-unsubscr...@lists.4d.com **********************************************************************
