Pat: I struggled with this for a few months. A bunch of research, help from the nug, and help from 4D Tech support, I think I found our problem. We will use a graphic application to create some graphics (icons / pictures etc). As is usual, Apple is getting more strict with each version of the OS for signing. They are permitting less ‘noise’ in the files.
Make of copy of your .4dbase to work with that is uncompiled. The goal is to make a clean development version that you can use from now on that will sign with 4D’s build tool. In Terminal issue the following: Pats-Mac-Pro: ~ pat$ codesign —force —deep -s “Developer ID Application: Pat (yourIDHere)” -fvvvv /PathTo/Your.4dbase/ This command goes through all the files in the .dbase directory and clears out things like finder attributes that are not permitted. If this does the trick you will see that the the application has been signed. If this works, make this your new development version. Subject to adding any new files into the .4dbase it should compile, build and sign using the 4D tool. Jody > On Mar 21, 2019, at 5:52 AM, Pat Bensky via 4D_Tech <[email protected]> > wrote: > > Using v17 > I've added our Apple OSX signing certificate to a client's app built with > 4D v17. It compiles and runs just fine. > I've added the same certificate to another app, using the same version of > 4D and the same compiler settings. However with this one, at the end of > compilation, I get the message "Code signature failed". > Any suggestions as to why it would work for one app but not for another? As > far as I can see, the settings are identical. > > Pat > ********************************************************************** 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] **********************************************************************
