I dunno, but I two things jump out at me: On Jun 18, 2017, at 20:06 , Graham Cox <graham....@bigpond.com> wrote: > > 2017-06-19 02:52:16 +0000 Disqualifying <DVTSigningCertificate: > 0x7ff548966ae0; name='3rd Party Mac Developer Installer: REDACTED, LLC > (V55NQxxxxN)’, […]
This is a Mac App Store certificate. If it’s “disqualifying” it only incidentally while looking for a Developer ID certificate, it sounds like this MAS certificate is no longer valid. Is that something to do with the certificate upgrade that happened a year or two ago? It’s not clear if this is just “oh, by the way”, or whether it has something important to do with the code signing failure. > 2017-06-19 02:52:28 +0000 Warning: usage of --preserve-metadata with option > "resource-rules" (deprecated in Mac OS X >= 10.10)! > 2017-06-19 02:52:28 +0000 > 2017-06-19 02:52:29 +0000 > /var/folders/_d/fcb3h3892y339vh632v_hz280000gn/T/XcodeDistPipeline.OPU/Root/Applications/xxxx.app: > resource fork, Finder information, or similar detritus not allowed Is there any chance you might have looked into the app package contents with the Finder some time, and caused (say) a “.DS_Store” file to be created? That’s the sort of thing this error seems to be talking about. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
