Hi all,

It’s that time of year, so it must mean it’s time for my annual 
frustration-fest that is dealing with code signing.

I just upgraded to a new Mac for development. I transferred everything from the 
previous Mac using migration assistant, and mostly it works fine. The transfer 
included Xcode 7.3.1 which is the version I’m currently using. It builds, runs 
and debugs the app fine. It also transferred all my keychain certs from the old 
machine.

Note that my old OS was 10.11, this new machine is 10.12.

So, I want to export the app with Developer ID codesigning, but it fails. 
Rather than a helpful error message, it just offers to reveal the logs to me in 
the Finder.

It’s unclear what the reason for the codesign failure is. The verbose log ends 
with:

2017-06-19 02:52:16 +0000  Disqualifying <DVTSigningCertificate: 
0x7ff548966ae0; name='3rd Party Mac Developer Installer: REDACTED, LLC 
(V55NQxxxxN)', hash='8F7B3791F5B1187CF09F12A4675A7188941EFCFE', 
certificateKind='1.2.840.113635.100.6.1.8'> due to certificateKind (input 
1.2.840.113635.100.6.1.13 doesn't match 1.2.840.113635.100.6.1.8)
2017-06-19 02:52:16 +0000  -[IDEDistributionProvisioning 
_signingCertificatesApplicableForTeamID:certificateKind:isForInstaller:error:]: 
identityCertificatesMatchingKind [kind=1.2.840.113635.100.6.1.13] = (
   "<DVTSigningCertificate: 0x7ff56ebc41a0; name='Developer ID Application: 
REDACTED, LLC', hash='33062E67AE94A0F6693358645C5BA6306CB8E2C9', 
certificateKind='1.2.840.113635.100.6.1.13’>”

)

The standard log ends with:

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
2017-06-19 02:52:29 +0000  /usr/bin/codesign exited with 1
2017-06-19 02:52:29 +0000 [MT] Proceeding to distribution step 
IDEDistributionSummaryStepViewController, context: <IDEDistributionContext: 
0x7ff5a4258d50; archive(resolved)='<IDEArchive: 0x7ff5a363f860>', 
distributionTask(resolved)='2', 
distributionMethod(resolved)='<IDEDistributionMethodDirectDistribution: 
0x7ff56e8e2620>', teamID(resolved)='V55NQxxxxN'>
        Chain (5, self inclusive):
        <IDEDistributionContext: 0x7ff5a4258d50; archive = '(null)', 
distributionMethod='(null)', teamID='(null)'>
        <IDEDistributionContext: 0x7ff5a321bde0; archive = '(null)', 
distributionMethod='(null)', teamID='(null)'>
        <IDEDistributionContext: 0x7ff53d458cf0; archive = '(null)', 
distributionMethod='(null)', teamID='(null)'>
        <IDEDistributionContext: 0x7ff596090550; archive = '(null)', 
distributionMethod='(null)', teamID='V55NQxxxxN'>
        <IDEDistributionContext: 0x7ff5a2072290; archive = '<IDEArchive: 
0x7ff5a363f860>', distributionMethod='<IDEDistributionMethodDirectDistribution: 
0x7ff56e8e2620>', teamID='(null)'>
</IDEDistributionContext: 0x7ff5a4258d50>
2017-06-19 02:53:36 +0000 [MT] Canceled distribution assistant


And the crtical log has only:

2017-06-19 02:52:29 +0000 [MT] Presenting: Error 
Domain=IDEFoundationErrorDomain Code=1 "Codesign failed" 
UserInfo={NSLocalizedDescription=Codesign failed}

(n.b. I’ve edited the above to remove any potential sensitive information)


I have no idea what the problem is. I have no idea what I’m doing, and I have 
no idea in detail how code signing works and what information a Developer ID 
certificate contains. But at root I can imagine it’s due to the machine being 
different (though possibly the OS version).

Looking at my assets at developer.apple, my new Mac isn’t listed as a 
registered device, naturally. When I try to add a registered device, it 
requests the name and UUID of the machine. I have no idea what these values are 
(well, the name I assume is the name I assigned it in the ‘Sharing’ 
preferences, but where is the UUID?). Apple expect me to type these things in.

This is a real pain point. Can anyone help? I have to resolve this urgently 
because we must be able to sign and release our apps.

—Graham


_______________________________________________

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

Reply via email to