Checking your IPA that won’t publish to the App Store

Need Flex Migration Help?

  • Adobe ends Flash player support in 2020
  • Flex apps will no longer function
  • We can help migrate your app

When publishing your app to the app store the process of debugging issues can be a little painful. The particular issue I was dealing with was the dreaded (and super vague) Application failed codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate . Apple isn’t terribly explicit about what possible problems can cause this, but they do offer some means of identifying what the internal issues are. Using X-code, generate an IPA using the “Archive” option in the “Project” menu on your top bar. Locate the newly created IPA and rename the extension to .ZIP. You should now be able to use your archive extractor to open the zip. Inside you should find the .app file for your application.  Using that .app you can run the following command

[sourcecode]codesign –verify -vvvv -R=’anchor apple generic and certificate 1[field.1.2.840.113635.] exists and (certificate leaf[field.1.2.840.113635.] exists or certificate leaf[field.1.2.840.113635.] exists)’ “Path to your .app file (no quotes, just the path)” [/sourcecode]

The output from this should contain more explicit messages about errors in your application, including missing files, bad extensions and/or library reference errors.  Correcting everything on this list and running the command again should provide you with an “all clear” message.  At this point your IPA should be good to go in distribution to the app store.


Location for Frameworks on IOS

[sourcecode]/Applications /[/sourcecode]

Comments are closed.