Re: Trouble code-signing in XC8
Re: Trouble code-signing in XC8
- Subject: Re: Trouble code-signing in XC8
- From: Sak Wathanasin <email@hidden>
- Date: Fri, 05 Aug 2016 20:08:27 +0100
- Dkim-filter: OpenDKIM Filter v2.10.3 mx1.network-analysis.ltd.uk 18CC02DEA7A
> 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.
Now I’d best go and sweep up all this hair I’ve pulled out...
_______________________________________________
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