Miyako, I think that, as usual, you identify the issue. I installed the 4D application as you describe and the problem doesn’t arise from anything it contained when I installed it. However...
The files with extended attributes are those backed up by Dropbox (which seems to add its own) and some third-party plugins and components which I have acquired (such as XLS II). I suspect the Finder has added them. As long as removing the attributes doesn’t hurt (and it doesn’t seem to hurt), the issue is easily solved; I build the application from within a method anyway, so using a couple of LEP calls, invoking xattr to remove the attributes and codesign to sign the application, is trivially easy and works well. Thanks Jeremy > On 14 Oct 2018, at 20:42, Keisuke Miyako via 4D_Tech <[email protected]> > wrote: > > Hello, > > are you sure you downloaded the official .dmg file from 4D, > and copied the application out of the disk image directly to a subdirectory > of the Applications folder? > > Finder attributes are automatically added whenever you transfer a file from > one Mac to another, > via HTTP or FTP download, AirDrop or E-Mail (nut not USB or shared drive). > > 2018/10/14 23:04、Jeremy Roussak via 4D_Tech > <[email protected]<mailto:[email protected]>>のメール: > 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. ********************************************************************** 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] **********************************************************************
