Re: Codesigning 3rd party framework
Re: Codesigning 3rd party framework
- Subject: Re: Codesigning 3rd party framework
- From: Seth Willits <email@hidden>
- Date: Tue, 05 Nov 2013 08:48:39 -0800
When you use —deep, "all signing options you specify [on the app bundle] will apply, in turn, to such nested content [as embedded frameworks, helpers, resources, etc]” which is not the correct thing that should happen.
https://devforums.apple.com/thread/203126?start=0&tstart=0
--
Seth Willits
On Nov 5, 2013, at 3:39 AM, Jakob Egger <email@hidden> wrote:
> Does anybody know why just specifying "--deep" in "Other Code Signing Flags" is wrong? Is it only a problem with Sparkle, or is there a general problem?
>
> In my app I just specified --deep and it seems to work!
>
> On 29 Oct 2013, at 10:37 pm, Shazron <email@hidden> wrote:
>
>> See http://furbo.org/2013/10/17/code-signing-and-mavericks/ he specifically
>> deals with your Sparkle.framework problem
>>
>>
>> On Tue, Oct 29, 2013 at 5:30 PM, Graham Cox <email@hidden> wrote:
>>
>>> Having just updated to Xcode 5.0.1, I can’t build one of our apps because
>>> it uses the Sparkle framework, which isn’t codesigned. Previously this
>>> wasn’t an issue but it seems Xcode is being a bit stricter than before.
>>>
>>> Is there a way I can codesign this module using my own credentials? I have
>>> little experience of dealing with these issues, most of the time I just
>>> hope it works and it does, but now it doesn’t I’m in a very tight spot. -
>>> I can’t easily downgrade to the older Xcode and I need this app built by
>>> tomorrow!
--
Seth Willits
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden