When upgrading an app - the "invalid binary" error... any suggestions?

Question

While upgrading an existing app, I'm getting the notorious:
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

Answer 1

I can't believe it, but after multiple-days of Code-Signing h*ll I fixed it! The app is now uploaded and 'in review".
For those interested in my solution, here is what I did.
I opened up the .xcodeproj package for a previous app we have in the app store (let's call it OtherApp) and then opened up project.pbxproj in BBEdit and looked at the sections for "Distribution" and they looked like this:
8418EBF90E90792200A3FDDA /* Distribution */ = {
isa = XCBuildConfiguration;
buildSettings = {
ARCHS = "$(ARCHSSTANDARD_32BIT)";
GCCC_LANGUAGESTANDARD = c99;
GCCWARN_ABOUT_RETURNTYPE = YES;
GCCWARN_UNUSEDVARIABLE = YES;
PREBINDING = NO;
SDKROOT = iphoneos2.0;
name = Distribution;
8418EBFA0E90792200A3FDDA /* Distribution */ = {
isa = XCBuildConfiguration;
buildSettings = {
ALWAYSSEARCH_USERPATHS = NO;
CODESIGNIDENTITY = "iPhone Distribution: My Company Name, Ltd.";
COPYPHASESTRIP = YES;
GCCPRECOMPILE_PREFIXHEADER = YES;
GCCPREFIXHEADER = OtherApp_Prefix.pch;
INFOPLIST_FILE = Info.plist;
PRODUCT_NAME = OtherApp;
PROVISIONING_PROFILE = "E6A3BCFE-372D-4623-AB15-44158ADA0E1B";
name = Distribution;
But in the project.pbxproj file for the app I was trying to upgrade (let's call it ThisApp) those sections looked like this:
84D2ED8E0E5B857A00CAA465 /* Distribution */ = {
isa = XCBuildConfiguration;
buildSettings = {
ALWAYSSEARCH_USERPATHS = NO;
ARCHS = "$(ARCHSSTANDARD_32BIT)";
GCCC_LANGUAGESTANDARD = c99;
GCCWARN_ABOUT_RETURNTYPE = YES;
GCCWARN_UNUSEDVARIABLE = YES;
PREBINDING = NO;
SDKROOT = iphoneos2.0;
name = Distribution;
84D2ED8F0E5B857A00CAA465 /* Distribution */ = {
isa = XCBuildConfiguration;
buildSettings = {
CODESIGNIDENTITY = "iPhone Distribution: My Company Name Ltd.";
COPYPHASESTRIP = YES;
GCCPRECOMPILE_PREFIXHEADER = YES;
GCCPREFIXHEADER = ThisApp_Prefix.pch;
INFOPLIST_FILE = Info.plist;
PRODUCT_NAME = ThisApp;
PROVISIONING_PROFILE = "00D072E0-3459-4AFF-911E-B31D325E7375";
"PROVISIONING_PROFILE[sdk=iphoneos*]" = "B260C653-9A45-372C-A472-31F1531EEA44";
name = Distribution;
So (after backing up the current version) I:
(1) deleted the 2nd "PROVISIONING_PROFILE" line (which is the developer provisioning profile - so I don't know what will happen now if I try to load it on my iPhone);
(2) cleaned targets;
(3) built again and the new compressed version uploaded!
Side-note not directly related to the above problem, but of technical interest:
I got another error at the next itunesconnect page saying that the "bundle identifier needed to be the same as the previous version". That was easy to fix though. I went back into Xcode and changed the bundle identifier from com.myactualcompanyname.${PRODUCT_NAME:identifier} back to com.yourcompany.${PRODUCT_NAME:identifier} (the original default value) which was the way we accidentally left it when we first built it in September. (It was our first app, so that snuck by us.) So apparently you can never adjust that once you upload an original app and have forgotten to change "yourcompany" for your actual company name. That's not so important though, and wasn't what was blocking being able to upload the app.
Anyway, it now uploaded successfully and is "in review"!
Clearly "something happened" to the project.pbxproj file between the time the app was first created in September and when the SDK was updated after that.
But it's in review now!
doug@sigh of relief