Obsolete Code Signing Resource Rules Path

The Code Signing Resource Rules Path build setting is no longer used as of Xcode 6. New projects created in Xcode 6+ do not define a value for this build setting. In addition, if your Xcode project is still defining a value for this build setting it can cause the Invalid Signature binary rejection. To resolve this cause of the error, remove values defined for this build setting using the following steps:

1. Open the project level build settings using the Xcode project editor.

2. Select the value portion of the Code Signing Resource Rules Path build setting and press delete.

3. Repeat step 1 for all app targets (main app, extensions, other plugins or frameworks that are bundled with your app).

4. Re-create the Xcode archive and re-submit the app.

Dot Files and non-HFS+ formatted hard drives

Dot files are a problem that result from copying an unzipped Xcode project to and from a non HFS+ formatted hard drive. Dot files are also referred to as Apple Double files, or resource forks. Use the following steps to diagnose and resolve this situation:

• Run the terminal command diagnostic in Technical Note TN2318 - Troubleshooting Failed Signature Verification > How do I check if my application's signature has been corrupted?

• Compare the command results with subsection: List of Signature Verification Failure Root Causes. The issue is diagnosed with a result stating:  

  resource missing: my.app/._*

• Follow these steps to remove the problematic files:

  The file prefixed with "._" is problematic and a was the result of copying certain Mac OS X files to a non-HFS+ formatted disk. These files are invisible to Finder but can be removed using the dot_clean utility. The Xcode Project Folder is the argument to dot_clean as illustrated below.

  dot_clean /path/to/My_Xcode_Project

• After running dot_clean on your Xcode project, create a new app archive and then re-attempt submission.  

• To prevent this issue, be sure to zip Xcode project folders using Finder before transferring them to a non-HFS+ formatted drives. 

Do Not Distribute Apps From Beta OS X or Beta Xcode

App Store apps are required to be built with GM versions of OS X and Xcode. If apps are instead built with a beta version of OS X or Xcode, they will be rejected on those grounds. Beta, Seed, Developer Preview and Pre-Release software are synonymous in this context.

Avoid special characters in Executable names

Executable files within your app that contain special characters (i.e. non-numeric, and non-alpha) can cause this rejection. To resolve the problem, change the Xcode target’s Product Name build setting from ${TARGET_NAME} to a string containing only alpha/numeric characters. Also, ensure the value of the Info.plist key "Executable file" is equal to ${EXECUTABLE_NAME}. If identified to be the cause, please file a bug report using Apple Bug Reporter identifying the problematic characters.