Can't submit app - "Invalid Signature - Code object is not signed at all"

Question

Ruben OP

Created Jun ’15

Replies 3

Boosts 0

Views 3.6k

Participants 1

Hello,

I have submitted my app build from xCode on May 30, 2015. It passed all validations during submission and successfully appeared in iTunes Connect.

Then I realized that there are few things that I want to fix before letting Apple start reviewing.

Starting from yesterday (June 9) I am trying to submit another build for the same application using the same configurations and same xCode method for submission, but what I get is:

"Invalid Binary" in the status line for all newly uploaded builds
An email from iTunes Connect after each build upload, with this error description:

Invalid Signature - Code object is not signed at all. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html

Once these issues have been corrected, you can then redeliver the corrected binary.

Regards,

The App Store team

Please note, that I am not getting any error message during uploading process in xCode, so it passes all the identity and code signing validation steps and successfully uploads the build.

Also the Distribution Certificate and Distribution Provisioning Profile are not changed, are the same what was used in case of successful submission on May 30.

I even rolled back all changes made since May 30 and built same version which was once accepted on May 30, but the new build again was marked with "Invalid Binary" and the "Invalid Signature" email was received.

Can you please help. I already have completed and prepared application, but can't submit because of this wired error.

Thanks,

Ruben

Boost

Answer 1

raid5 OP

Jun ’15

I had this same exact issue. My specific issue was related to a 3rd party framework I was including in the project. Once I removed the framework, my submission went through successfully and did not get kicked into the Invalid Binary state. I'm not sure exactly what changed with regards to the validation process by Apple, but this was extremely frusterating. Hope this helps!

1

Answer 2

Ruben OP

Jun ’15

Thank you for your reply.

The problem really appeared to be in the 3rd party SDK I used in my project. I was using the HockeyApp SDK, and included all the files coming with the SDK into my project. There were some redundant files after removing which the Apple validation process stopped complaining about "Invalid Binary".

But the strange thing is that the app submitted on May 30 with previous configurations (with redundant files) didn't produce the error, but the app with same configurations submitted after Jun 9 produces the "Invalid Binary" error. So there is definitely something changed in the Apple validation procedure during that period.

0

Answer 3

fstark OP

Jun ’15

I got this issue when I added a .js file to a project, and the .js file was automatically added to the files my app produce (it was a file for local execution and should not have been shipped within the app).

The hard to understand complain was that the .js file is technically an executable and was not signed, hence the whole app was rejected. When I removed the .js file from the project build, it worked.

Check if you have .js, .sh, .py or whatever other files that Apple validation scripts may think are executable included in you end product.

0