• 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
Correct method to codesign frameworks?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Correct method to codesign frameworks?


  • Subject: Correct method to codesign frameworks?
  • From: Bernie Maier <email@hidden>
  • Date: Sat, 07 May 2016 00:11:12 +1100

OK, so I'm on a bit of a roll here after my previous question was successfully answered, so I now have a question about code signing frameworks. I suspect this may have been asked previously on this list, but my searching foo is not up to finding it right now.

The OS X project I have inherited builds a framework used by the other parts of the app (it's an app with a bunch of plugin bundles). If I try to code sign the framework simply by specifying a code signing identity in the Xcode build settings for the framework target, the build fails with an error saying my code is unsigned when I try to sign it. Looking closely, it is attempting to sign foo.framework/Versions/A.

Tech Note TN2206 <https://developer.apple.com/library/mac/technotes/tn2206/_index.html> says:

codesign says my code is unsigned when I try to sign it.
  Make sure all nested code is already signed and its signature is valid.
  Xcode will take care of this for you if you let it handle your code signing
  tasks.

Well, I'm trying to let Xcode handle my code signing tasks, so either the tech note is lying, or something is strange about how this project is set up. The Xcode version is 7.2.1 by the way, and the system I'm building on is OS X 10.11.4.

I have worked around the problem by adding a run script build phase to the framework target that explicitly code signs the executable within the framework bundle, i.e. foo.framework/Versions/A/foo. But the documentation seems to suggest this is unnecessary (for a single-versioned framework, which my framework is) and code signing the the framework itself Should Just Work(TM).

So, what is the correct way to code sign a framework target? Or why would code signing a framework target fail? The latter question may highlight something set up incorrectly in my project.

_______________________________________________
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


  • Follow-Ups:
    • Re: Correct method to codesign frameworks?
      • From: Quincey Morris <email@hidden>
  • Prev by Date: Re: How to convert a project using legacy build location to modern?
  • Next by Date: Re: Correct method to codesign frameworks?
  • Previous by thread: Re: How to convert a project using legacy build location to modern?
  • Next by thread: Re: Correct method to codesign frameworks?
  • Index(es):
    • Date
    • Thread