Code signing, Helper tools/apps, Recent changes
Code signing, Helper tools/apps, Recent changes
- Subject: Code signing, Helper tools/apps, Recent changes
- From: Seth Willits <email@hidden>
- Date: Thu, 07 Aug 2014 17:22:51 -0700
Not knowing any better, my helper tools and helper apps have always been dumped into Resources. (In my defense, Xcode's Copy build phase does not offer a better location to copy them to.)
Reading the recent changes in TN2206, the "Nested code" section clearly explains that doing that is a bad idea:
"… Conversely, putting code into [the Resources folder] will cause it to be sealed as data (resource) files, causing trouble during updates."
1) I'm curious as to what the above warning means. If I verify and assess (on 10.10 DP5) my app that contains signed single-file tools or helper .app bundles in the Resources folder, it passes just fine. spctl accepts it, and codesign --deep validates the app. No complaints. Is it expected to fail?
2) The correct place to put tools and apps bundled inside of a .app seems to clearly be .app/Contents/Helpers. But what about code bundled inside of a framework where there is no Contents folder? The technote seems to suggest if there's a Versions folder (as there is for frameworks) there cannot be a Contents folder next to it. Should it instead be next to the Resources folder? eg: .framework/Versions/A/Contents/Helpers/... ?
--
Seth Willits
_______________________________________________
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