• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Trouble code-signing in XC8
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Trouble code-signing in XC8


  • Subject: Re: Trouble code-signing in XC8
  • From: Alex Zavatone <email@hidden>
  • Date: Fri, 05 Aug 2016 14:24:53 -0500

On Aug 5, 2016, at 2:08 PM, Sak Wathanasin wrote:

>
>> On 5 Aug 2016, at 17:16, Stéphane Sudre <email@hidden> wrote:
>>
>>
>> On 5 août 2016, at 16:31, Sak Wathanasin wrote:
>>
>>> ...The build log for the Release build shows that framework sub-projects don't sign their targets (but dylibs and helper tools do) and when it comes to sign the app, it complains that
>>>
>>> …/MyApp/Contents/Frameworks/xxx.framework: code object is not signed at all
>>>
>>> Is there some new setting in XC8 that I've missed or is this done a different way now?
>>
>> I've seen the same issue here.
>>
>> Adding the --deep extra flag to the code signing settings of the MyApp project solved the issue.
>>
>> Not sure this is not a bug though (I've already filed a bug report).
>
> Thanks for the response.
>
> I created a toy app with a toy framework, and, guess what? - it built properly. The build logs show that XC8 does indeed work differently: it now copies the f/w over, then signs it. Which makes sense, except that it doesn’t do it for projects that have been migrated from prev versions of XC. So, for those of you bringing older projects into XC8: go to the build phase where you copy frameworks to your app bundle, remove them and add them back in. Looking at the diffs in BitBucket, it looks like this adds "CodeSignOnCopy" attributes to the relevant items in the project file.

Yeah, I'm really glad you mentioned this little tidbit and glad you found it.

I've been looking at the build settings in my framework and wondering how it magically works without requiring code signing, knew about that tag and wondered, "I wonder when and under what conditions this gets turned on - and then what do we do?"

Noting that, it's expected that this will rear its head at some point when it's required that we codesign our frameworks.  Considering just how much we appreciate the hair that is present on top of our heads, what are the conditions where code sign on copy is turned on and what is the process to support that?

Does anyone know?

> Now I’d best go and sweep up all this hair I’ve pulled out...

Let me help you with that.

http://www.redmax.com/products/blowers/ebz8500rh/

Make it your neighbors' problem.

But if you insist on being a good neighbor, this should do the job…

http://www.homedepot.com/p/ECHO-165-mph-391-CFM-Gas-Shredder-Vacuum-ES-250/202827820

Good luck with the cleanup and the code signing.

Alex Zavatone


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


References: 
 >Trouble code-signing in XC8 (From: Sak Wathanasin <email@hidden>)
 >Re: Trouble code-signing in XC8 (From: Stéphane Sudre <email@hidden>)
 >Re: Trouble code-signing in XC8 (From: Sak Wathanasin <email@hidden>)

  • Prev by Date: Re: Trouble code-signing in XC8
  • Next by Date: Xcode 7.3 commit to git repo "Couldn't communicate with helper application"
  • Previous by thread: Re: Trouble code-signing in XC8
  • Next by thread: Xcode 7.3 commit to git repo "Couldn't communicate with helper application"
  • Index(es):
    • Date
    • Thread