Re: Correct method to codesign frameworks - solved
Re: Correct method to codesign frameworks - solved
- Subject: Re: Correct method to codesign frameworks - solved
- From: Bernie Maier <email@hidden>
- Date: Mon, 09 May 2016 16:36:22 +1100
Quincey Morris:
On May 8, 2016, at 20:43 , Bernie Maier <email@hidden>
wrote:
>
> this smells a little bit like voodoo
A little bit of voodoo might be unavoidable. I take it as a given then newer
versions of Xcode do some kind of fixup on older sets of project settings,
but that you can’t necessarily rely on this producing the same result as
starting over with new settings and targets, especially if the old project
was never entirely correct.
Sure, but I'd feel a lot more comfortable if that voodoo expressed itself in
some kind of visible difference in the project settings. So, merely discussing
this with someone is prodding me to look harder in the differences between the
two targets.
I think you are right about the old project not being entirely correct,
because I believe I have found the culprit. I was kind of fixated on looking
at the build settings in project.pbxproj, but creating the new framework
target created a nice new, clean Info.plist file. And comparing that to the
one for the existing target reveals the smoking gun: the old target's
Info.plist omits the CFBundleExecutable key. So if code signing is supposed to
work from the inside out, then it can't do that without being told what the
inside is. May that be a lesson for anyone with weird code signing issues on
old projects.
So, thanks for the discussion. It didn't provide the answer directly, but it
helped steer me along.
_______________________________________________
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