Re: Annual codesign pain point

2017-06-19 Thread Alex Zavatone 
Well, I guess that didn't come through.

I was wondering if you still get that certificate mismatch now that the image 
is corrected.


Sent from my iPhone

> On Jun 19, 2017, at 8:29 AM, Alex Zavatone  wrote:
> 
> 
> ___
> 
> 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/zav%40mac.com
> 
> This email sent to z...@mac.com
___

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

Re: Annual codesign pain point

2017-06-19 Thread Alex Zavatone 

___

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

Re: Annual codesign pain point

2017-06-18 Thread Shane Stanley 
On 19 Jun 2017, at 3:12 pm, Graham Cox  wrote:
> 
> Not sure why this wasn’t picked up in my previous builds though, since I was 
> compiling on 10.11.

The change was made in 10.12.

-- 
Shane Stanley 
, 


___

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

Re: Annual codesign pain point

2017-06-18 Thread Graham Cox 
Bingo!

I had one image resource with a resource fork. Not sure why this wasn’t picked 
up in my previous builds though, since I was compiling on 10.11. But that does 
seem to have been the issue.

Thanks to Alex for his unending patience offline sifting through all the 
signing certificate issues, which were probably a red herring after all.


—Graham




> On 19 Jun 2017, at 1:58 pm, Shane Stanley  wrote:
> 
> On 19 Jun 2017, at 1:06 pm, Graham Cox  wrote:
>> 
>> resource fork, Finder information, or similar detritus not allowed
> 
> See: 

___

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

Re: Annual codesign pain point

2017-06-18 Thread Shane Stanley 
On 19 Jun 2017, at 1:06 pm, Graham Cox  wrote:
> 
> resource fork, Finder information, or similar detritus not allowed

See: 

-- 
Shane Stanley 
, 


___

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

Re: Annual codesign pain point

2017-06-18 Thread Quincey Morris 
I dunno, but I two things jump out at me:

On Jun 18, 2017, at 20:06 , Graham Cox  wrote:
> 
> 2017-06-19 02:52:16 +  Disqualifying  0x7ff548966ae0; name='3rd Party Mac Developer Installer: REDACTED, LLC 
> (V55NQN)’, […]

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 +  Warning: usage of --preserve-metadata with option 
> "resource-rules" (deprecated in Mac OS X >= 10.10)!
> 2017-06-19 02:52:28 +  
> 2017-06-19 02:52:29 +  
> /var/folders/_d/fcb3h3892y339vh632v_hz28gn/T/XcodeDistPipeline.OPU/Root/Applications/.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

Re: Annual codesign pain point

2017-06-18 Thread Alex Zavatone 
Codesigning sucks. Please contact me off list and I will be happy to try and 
help you through it.

- Z

> On Jun 18, 2017, at 10:06 PM, Graham Cox  wrote:
> 
> 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 +  Disqualifying  0x7ff548966ae0; name='3rd Party Mac Developer Installer: REDACTED, LLC 
> (V55NQN)', 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 +  -[IDEDistributionProvisioning 
> _signingCertificatesApplicableForTeamID:certificateKind:isForInstaller:error:]:
>  identityCertificatesMatchingKind [kind=1.2.840.113635.100.6.1.13] = (
>   " certificateKind='1.2.840.113635.100.6.1.13’>”
> 
> )
> 
> The standard log ends with:
> 
> 2017-06-19 02:52:28 +  Warning: usage of --preserve-metadata with option 
> "resource-rules" (deprecated in Mac OS X >= 10.10)!
> 2017-06-19 02:52:28 +  
> 2017-06-19 02:52:29 +  
> /var/folders/_d/fcb3h3892y339vh632v_hz28gn/T/XcodeDistPipeline.OPU/Root/Applications/.app:
>  resource fork, Finder information, or similar detritus not allowed
> 2017-06-19 02:52:29 +  /usr/bin/codesign exited with 1
> 2017-06-19 02:52:29 + [MT] Proceeding to distribution step 
> IDEDistributionSummaryStepViewController, context:  0x7ff5a4258d50; archive(resolved)='', 
> distributionTask(resolved)='2', 
> distributionMethod(resolved)=' 0x7ff56e8e2620>', teamID(resolved)='V55NQN'>
>   Chain (5, self inclusive):
>distributionMethod='(null)', teamID='(null)'>
>distributionMethod='(null)', teamID='(null)'>
>distributionMethod='(null)', teamID='(null)'>
>distributionMethod='(null)', teamID='V55NQN'>
>distributionMethod=' 0x7ff56e8e2620>', teamID='(null)'>
> 
> 2017-06-19 02:53:36 + [MT] Canceled distribution assistant
> 
> 
> And the crtical log has only:
> 
> 2017-06-19 02:52:29 + [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/zav%40mac.com
> 
> This email sent to z...@mac.com

___

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

Annual codesign pain point

2017-06-18 Thread Graham Cox 
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 +  Disqualifying  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 +  -[IDEDistributionProvisioning 
_signingCertificatesApplicableForTeamID:certificateKind:isForInstaller:error:]: 
identityCertificatesMatchingKind [kind=1.2.840.113635.100.6.1.13] = (
   "', 
distributionTask(resolved)='2', 
distributionMethod(resolved)='', teamID(resolved)='V55NQN'>
Chain (5, self inclusive):






2017-06-19 02:53:36 + [MT] Canceled distribution assistant


And the crtical log has only:

2017-06-19 02:52:29 + [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