I don't know about your framework but a .a file is a static library. Are you sure that you're really linking to it at runtime rather than build time? Perhaps it should be a .dylib for runtime linking, or for build time linking you don't include it in your distribution at all.
Sent from my iPhone On Nov 29, 2011, at 5:26 PM, Gideon King <gid...@novamind.com> wrote: > Hi, I'm having a problem with code signatures. My app has about 20 > executables in it, all of which I sign using the codesign -f -s command. All > of them are signed in exactly the same way, and when I run codesign --verify > --verbose, it says they are all valid. > > When I submit the application to the app store, it says that two of the > signatures are missing or invalid. One is on one of my frameworks and the > other one is on a .a file. > > How can I work out what is going wrong with the signature on these two files, > given the fact that they pass verification and are signed the same way as the > ones that are accepted? > > > Thanks > > Gideon > > > > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > 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: > http://lists.apple.com/mailman/options/cocoa-dev/quixote%40dulcineatech.com > > This email sent to quix...@dulcineatech.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
