![]() You’ll see the same thing if you check the binary using the command line: ![]() #XSCOPE MAC INSTALL#In fact, if you try to download and install the resulting app, Gatekeeper will notify your customers that your app is damaged and can’t be opened, with a default button to move it to the Trash: Things like your app’s entitlements will cause the resulting bundles to not be valid. As it does this, it applies the parameters for the top-level bundle to all the nested bundles. The reason is that -deep recursively signs the nested bundles. Specifying this option in “Other Code Signing Flags” will get rid of the error during the build, but all you’re doing is just postponing the pain. In the past, many developers have relied on codesign‘s -deep option to make sure the entire bundle is signed. So how do you go about fixing this? The Wrong Way The codesign command is reporting that “code object is not signed at all” and Xcode is adding the “In subcomponent” to tell you which framework is at fault (it could just have easily been HockeyApp or any other third-party framework you use.) In subcomponent: /Users/craig/Projects/Mac/xScope/build/Release/xScope.app/Contents/Frameworks/ameworkĬommand /usr/bin/codesign failed with exit code 1 Users/craig/Projects/Mac/xScope/build/Release/xScope.app: code object is not signed at all usr/bin/codesign -force -sign D2A3FE1814B0BA31B1924F1C3C3B5C89643FBED5 -requirements =designated\ =>\ anchor\ apple\ generic\ \ and\ identifier\ \"xScope\"\ and\ ((cert\ leaf\ exists)\ or\ (\ certificate\ 1\ exists\ and\ certificate\ leaf\ exists\ \ and\ certificate\ leaf\ =\ \"RYQWBTQRPT\"\ )) /Users/craig/Projects/Mac/xScope/build/Release/xScope.app Using code signing identity "Developer ID Application: The Iconfactory" Setenv CODESIGN_ALLOCATE /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate So what happens when you do your first app build on 10.9 using Xcode 5.0.1? If you embed a framework that’s unsigned, like the very popular amework, you’ll see a message during the final CodeSign build phase: (Yes, I realize this essay is going to break the NDA, but since Apple is asking us to submit apps for Mavericks, I want as many developers as possible to avoid the utter confusion I faced earlier this week.) The Effect It’s taken me several days to understand what these changes are, and with the help of Perry Kiehtreiber on the developer forums, I’d like to share what I’ve learned. #XSCOPE MAC UPDATE#The result is that you’ll need to update your Xcode projects as soon as you start building on 10.9. These nested bundles are things like helper executables, embedded frameworks, plug-ins and XPC services. ![]() app) if any nested bundle in that package is unsigned. Very simply put, you can no longer sign a bundle (like your. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |