Re: Annual codesign pain point

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 (Coco

Re: Annual codesign pain point

___ 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.co

Re: Annual codesign pain point

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.ap

Re: Annual codesign pain point

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,

Re: Annual codesign pain point

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-de

Re: Annual codesign pain point

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

Re: Annual codesign pain point

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

Annual codesign pain point

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 Xc