On May 6, 2016, at 06:11 , Bernie Maier <apple-xc...@worklists.blurk.net> wrote: > > 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.
This one might be harder to get a clear answer on. To start with, can you clarify a couple of things. — When you say “the build fails”, which target did you ask to be built? If it’s the app, which target within the build phases did the error relate to? If it’s the app, what happens if you build just the framework explicitly? — Is the framework that caused the error (a) a plugin bundle or (b) a private, embedded framework of the app that’s used by plugins, or (c) something else? — If this is something to do with plugins, what subdirectory are you putting them in? The tech note you referred to has a section that’s a sort of checklist for embedded bundles. Did you do everything it said to do?
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
