Xcode 7 Invalid Signature in Frameworks

Apparently this is not just something that was integrated into XCode 7, but seems to be something on Apple's Servers that has changed. When I build and upload the same binary from XCode 6.4 I get exactly the same error now. Does anyone know how to resolve this cause I have no **** clue

Hello,

We have the same problem on our side since we wanted to submit our application + the WatchKit 1 extension:

We have discovered one or more issues with your recent delivery for "iCoyote10 Test". To process your delivery, the following issues must be corrected:

Invalid Signature - The binary with bundle identifier 'com.moncoyote.icoyote10test.watchkitextension' at path [iCoyote10 WatchKit 1 Extension.appex] 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). 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.

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

Our understanding is that iTunesconnect looks to sign the application again, leading to this invalid signature situation.

We're trying to clean everything on our build machine to see if it changes anything.

We always had three profiles so far. One Dev to debug on a device, an AppStore one for the store and an adhoc for TestFlight (the old one, but we kept it for apples TestFlight). Apparently since the last weekend you can't do that anymore and have to sign your app with the AppStore profile at least that's what I did this time and it seemed to have worked so far. I also changed the signer from iPhone developer to iPhone distribution but I'm not sure if this was necessary (will try that again with the defaults next week). Maybe that helps you too: sign with the AppStore profile if you didn't do this before.

We stopped trying submitting our application + Watch Kit 1 extension since it keeps failing since yesterday.

We've tried our application + Watch Kit 2 extension and it works fine...

Very weird, sounds like Watch Kit 1 extension can not be submited anymore.

Dear developer,

We have discovered one or more issues with your recent delivery for "MyApp". To process your delivery, the following issues must be corrected:

Invalid Signature - The binary with bundle identifier 'com.mycompany.myframework' at path myframework.framework] 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). 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.

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

Regards,

The App Store team

This is also happening to me with my app. I don't have a watchKit extension, just a dynamic framework that i created. My BitCode is off for all my targets as well, and I've tried to revoke and generate all provisioning profiles and codesigning certificates. I also tried signing the framework with a wildcard certificate, but to no avail. I tried everything that email told me to try.

Is this issue solved? Is there anything that I can do to submit to iTunesConnect?

In our case we had forgetten the CODE_SIGN_RESOURCE_RULES_PATH value set in second target which is a Today Extension. Clearing the value for Code Sign Resource Rules Path in each target resolved the issue.