The binary code of the downloaded file is not correct. Signature Invalid or Not Signed with Apple Submission Certificate

Question

The selected binary is not valid. Signature Invalid or Not Signed with Apple Submission Certificate

receiving this error message. starting from day 2 .. tried all googlings .. its still there

Answer 1

After two days of struggle with this problem, the solution for me was to make sure that there are no two files that differ only in capitalization. Thus, Foo.png and foo.png in the same directory in your application will cause this error.

Here's what you need to check that I collected from different sites during these two days:

• check the final steps in the assembly log ProcessingProductPackaging and CodeSign
• make sure that you do not accidentally include .svn directories or similar
• make sure that you have the correct distribution profile in the project settings for the release mode and that it is not overridden by the target settings.
• in your pbxproj file, check the lines PROVISIONING_PROFILE and CODE_SIGN_IDENTITY for release mode or delete them and set the correct profile in the project settings again.
• use the Finder command instead of the zip terminal command
• check code output -vvvv MyApp.app
• check the output of the -dvvvv code MyApp.app
• check the output of the code --verify -vvvv -R = 'anchor apple generic and certificate 1 [field.1.2.840.113635.100.6.2.1] exists and the certificate sheet [field.1.2.840.113635.100.6.1.4] exists' MyApp.app
• If downloading using Safari does not work, try Firefox Icon
• should be 57x57
• use the application loader to get a more informative error message
• There should be no spaces or special characters anywhere in the zip download path.
• check your keychain: do you have a distribution certificate associated with the private key?
• make sure you install the active SDK on the device and not the simulator when creating
• open the .app file with Show Contents and check if it contains an embedded.mobileprovision file with the UUID of your distribution profile and the _CodeSignature folder with CodeResources inside
• make sure the package ID matches the AppID. For AppID XYZ.com.mycompany. * Valid package identifier is com.mycompany.myappname
• build on Mac Extended file system, not fat32
• try to remove provisioning profiles from Xcode, empty caches (Xcode menu → Empty caches), restart Xcode, add profile again

Answer 2

If you follow the instructions at http://developer.apple.com/iphone/manage/distribution/index.action , I can come up with the following things that might cause this error:

• The profile / key / security profile used for signing was incorrect
• Certificate has expired
• Zip does not work (it contains a couple of symbolic links that will be broken if you do not zip, as the instructions say)
• Your application suite has a license.plist file

Answer 3

After upgrading to Xcode 4, my Distribution build messed up with my Release version in the Schema configuration. I was able to fix it by doing the following:

• In Xcode 4, go to Product> Manage Schemes ...
• Select a goal / scheme, click the "Change" button
• Select action "Archive"
• Change configuration configuration from version to distribution

I received an "Invalid Binary File" and "Invalid Signature" message from Apple after downloading to iTunes Connect. They check and verify my settings, certificates, and other build settings, and CANNOT find the problem. Suppose my archive schema was set up to create Release, not distribution. Very lame and very upset!

Answer 4

I fixed this by adding two new keys to my payment resource - application identifier and key-key groups:

<plist version="1.0"> <dict> <key>application-identifier</key> <string>T9YRD11G97.com.duncancampbell.fontagious</string> <key>get-task-allow</key> <true/> <key>keychain-access-groups</key> <array> <string>T9YRD11G97.com.duncancampbell.fontagious</string> </array> </dict> </plist> 

I got "T9YRD11G97" from the AppID in the training profile and "com.duncancampbell.fontagious" from the BundleID in iTunesConnect.

Hope this helps.

Answer 5

This part of the process can be very unpleasant. I'm sorry that you already spent two days on this, but it looks like you're close.

To follow Lauri’s response, have you checked the information in the “Verifying the distribution build build” section of the instructions for creating the distribution application?

In particular, check that you included the correct file "embedded.mobileprovision" in the assembly, and also confirmed that the application was signed with the correct certificate?

Answer 6

For me, it was a space in the name of my project that caused an invalid signature error. When I checked the build log, I looked at the lines related to the distribution certificate and saw that there was a space in the file path. Removing a place in the name of my project fixed it, I hope this saves someone a lot of trouble.