Tuesday, July 12, 2011

Resolving code signing issues

/Developer/Applications/Utilities/Application Loader does not work.

You need to sign and deploy your app from within XCode 4.

  1. Under Project/Code Signing options set Code Signing Identity to your "3rd Party Mac Developer Application:.." certificate.
  2. If you link to static libraries they will be installed into the archive by default and they will cause code verification to fail since they don't have code signing option. To prevent this error open the xcodeproj file of static library and set Build Settings/Deployment/Skip Install to Yes.
  3. Select Product/Archive then Validate and Submit.
at No comments:
Subscribe to: Posts (Atom)

How to recover from Mac Book Pro catastrophes

Synopsis DISCLAIMER: This article applies to Intel based MacBook Pro 4th generation models with a Touch Bar (2006-2020.) The methodology giv...

  • Dealing with Help Viewer cache
    It is pain in the neck to deal with Help Viewer cache when developing your Help documents. After updating your indexes with Help Indexer, yo...
  • How to detect memory leaks in OS X Applications
    In this tutorial I am going to demonstrate how to detect memory leaks in your OS X applications. We are going to use XCode development envi...
  • Target-Action Design Pattern
    The target-action approach to event-driven systems allows for a much greater deal of dynamism when compared to other, more static approaches...