Odd, I was sure a developer provisioning profile worked before? Anyway, I generated an AdHoc provisioning profile and that fixed the original error. Great, time to create a build with an App Store profile, I thought. I create one, and Application Loader rejected it with the following:
ERROR ITMS-90035: "Invalid Signature. A sealed resource is missing or invalid. The binary at path [Pushdown.app/Pushdown] contains an invalid signature. 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"
I went back and made the provisioning profile again to be very sure it was for Distribution, same problem. Created a new certificate and then a new Distribution profile, same problem. Looking around the web, I see this is a known issue and fairly new:
http://stackoverflow.com/questions/29859996/error-itms-90035
Another thread here:
http://stackoverflow.com/questions/29859996/error-itms-90035
I had a look inside the create .ipa file but couldn't find anything .sh related so maybe not relevant.
Most feedback is xcode related though, is this something you're aware of Paul?
Twitter: @itanican
Facebook: https://www.facebook.com/PushdownGame
Website: www.push-down.com