CodeSign problems (one solution.)
This is an add-on to Dave’s posting on ._ (dot underscore) files and CodeSign errors (see http://shortpath.blogspot.com/2009/07/codesign-error-and-fbconnect-library.html.) My problem was different, but started with repeated:
“The binary you uploaded was invalid. The signature was invalid, or it was not signed with an Apple submission certificate.”
Note: I wasn’t able to compress the file using find (I suspected coincidentally, although now I don’t believe it. I got that common error of a few K instead of the expected Megabytes) so I was forced to use command line zip. Normally after a few tries the compress works and gives a good result, but this time it didn’t.
I’ve been shipping these binaries (from these configuration files w/o change) for a while now. I did the usual; exit/restarted XCode, double checked the project settings and active target settings, reviewed the Build Results log, even flushed XCode caches and (God, it felt like Windows) doing a machine reboot. Nothing helped. Google searches told me that Application Loader might give some useful error messages.
I started using the “Application Loader” and got the message:
” a sealed resource is missing or invalid codesign_wrapper-0.7.3: failed to execute codesign(1)”
Anyway, trying everything I could for a couple of hours and after reading Dave’s posting, I ended up doing a clean SVN checkout to a new location, deleting all .svn subdirectories (find . -name \.svn -exec rm -rf {} \; -print) and attempting again. This time things worked fine.
Note: I could easily compress using find’s “compress file” and didn’t need to manually zip. Further I was able to use iTunes Connect and not need Application Loader.
As others have said, this was very frustrating, and I hope this helps save others this pain.