Friday, October 18, 2013 [Tweets] [Favorites]

Code Signing and Mavericks

Craig Hockenberry:

Very simply put, you can no longer sign a bundle (like your .app) if any nested bundle in that package is unsigned. These nested bundles are things like helper executables, embedded frameworks, plug-ins and XPC services.

The result is that you’ll need to update your Xcode projects as soon as you start building on 10.9. 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.

Apple has been asking developers to update their apps for Mavericks, but the process for doing so is fragile and poorly understood.

Update (2013-12-20): The storeagent problem is still not fixed. It seems to be impossible to build an app for the Mac App Store unless you are using Mac OS X 10.8 and Xcode pre-5.

Update (2013-12-28): My customers are also having problems with 10.9 storeagent installing the version of my app that was built using 10.8.

3 Comments

[...] Xcode 5 still hasn’t restored the AppleScriptability that Xcode 3 had, and there’s undocumented voodoo that you need to apply just so that previously working projects will continue to [...]

[...] are also still major problems with code signing. I am holding off submitting updates to the Mac App Store because there’s a good chance that [...]

[...] is what I’m seeing as well. Given that the “storeagent: Unsigned app” Mavericks bug that can prevent Mac App Store apps from launching is still present in 10.9.2, I’m glad that [...]

Stay up-to-date by subscribing to the Comments RSS Feed for this post.

Leave a Comment