When upgrading an app - the "invalid binary" error... any suggestions?
The binary you uploaded was invalid. The signature was invalid, or it was not signed with an Apple submission certificate.
error.
I've gone through everything step-by-step and did all sorts of forum searches, but I can't seem to find a solution to this.
Some particulars:
1. I do have the distribution certificate in my keychain, and it appears to be associated with my certificate as the agent. The provisioning profile is also visible in the Xcode organizer, with no "yellow warnings" about there not being an identity associated with it or anything like that.
2. When building (and doing all the cleaning of targets etc.) the Code Signing for the target is set to iPhone Distribution: mycompany name, which is properly selectable from the popup menu.
3. The build succeeds and I check the build results and CodeSigning is in there, as well as the embedded provisioning profile and the app name is correct.
4. Examining the created package contents, Code Signing is in there as well, and also the embedded provisioning profile.
5. The app ID I used for the distribution provisioning profile is the same app ID I used for the original app. However I did create a new distribution provisioning profile because certs had expired and I changed the name of the distribution provisioning profile. But the distribution cert is now up-to-date and the app ID is the same as it always was.
6. It's not anything like an invalid Icon.png or anything like that, because that didn't change from the original version. This is just an update.
7. The developer provisioning profile works fine and I can load and run the app on my iPhone.
If anybody has any ideas I would be grateful. I've been in code signing h*ll for two days now.
Thanks,
doug
MBP C2D 17", Mac OS X (10.5), 3.0 GB RAM