ITMS-90034: Missing or invalid signature

After uploading a new App to the App Store Connect i receive an e-mail stating:

ITMS-90034: Missing or invalid signature - The bundle '...' at bundle path 'Payload/...' is not signed using an Apple submission certificate.


The App don't use any capability.

I've used Xcode to upload, as in a previous App which now is on the App Store.

All the apps use the default configuration: "Automatically manage signing", Provisioning profile "Xcode Managed Profile", Signing Certificate Apple Development: ############

The requested Signing Certificate is present in the keychain in 3 versions, the last one is valid (the older 2 are revoked).


What I should correct?

Up vote post of Luca_65 Down vote post of Luca_65
49k views
Posted by
Luca_65
Reply
Add a Comment

Replies

We are facing the exact same issue, but for an exiting app which we never had any issues with earlier. We didn't really change anything, so we are not sure why this just start happening.
We are using fastlane match for signing and bitrise for uploading to the app store.

Posted by
ine
Up vote reply of ine Down vote reply of ine
Add a Comment

+1

Posted by
HelloJZ
Post not yet marked as solved Up vote reply of HelloJZ Down vote reply of HelloJZ
Add a Comment

Same happen to our application too. Signing was done Fastline in CI and nothing has changed on that part

Posted by
TuOki^
Up vote reply of TuOki^ Down vote reply of TuOki^
Add a Comment

+1

Posted by
erqqfqwfeqwg
Up vote reply of erqqfqwfeqwg Down vote reply of erqqfqwfeqwg
Add a Comment

+1

Posted by
projectCharli
Up vote reply of projectCharli Down vote reply of projectCharli
Add a Comment

Same here +1

Posted by
projectCharli
Up vote reply of projectCharli Down vote reply of projectCharli
Add a Comment

+1

Posted by
Boxia Inc
Up vote reply of Boxia Inc Down vote reply of Boxia Inc
Add a Comment

+1

Posted by
lafappbrica
Post not yet marked as solved Up vote reply of lafappbrica Down vote reply of lafappbrica
Add a Comment

I am also facing this exact issue just today. This is a recent issue as I have updated another app over the weekend.

Not exactlyl sure what's changed.

Posted by
eigen
Up vote reply of eigen Down vote reply of eigen
Add a Comment

I found a solution that worked for me.


Hope it works for you as well:

- Add "--deep" to the "Other Code Signing Flags" Build Setting.

- Clean, Build, Archive.

- Resubmit


Good luck.

Posted by
eigen
Up vote reply of eigen Down vote reply of eigen
Add a Comment

Add "--deep" to the "Other Code Signing Flags" Build Setting.

Please don’t use 

--deep
. My 
--deep
Considered Harmful post explains why.

If 

--deep
is helping that suggests you have a problem with the way that you’re signing your product. See my Signing a Mac Product For Distribution post for recommendations on how to do that properly.

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware 

let myEmail = "eskimo" + "1" + "@apple.com"
Posted by
eskimo
Up vote reply of eskimo Down vote reply of eskimo
Add a Comment

Did apple do any changes lately?
Right now our iOS deployment pipeline is blocked because of this so it's acutally quite cirtical. As mentioned in my earlier post - we have not changed anything so it seems like something may have happened on your side?

Posted by
ine
Up vote reply of ine Down vote reply of ine
Add a Comment

+1

Posted by
pepitoGrillo
Up vote reply of pepitoGrillo Down vote reply of pepitoGrillo
Add a Comment

+1

Posted by
btamas27
Up vote reply of btamas27 Down vote reply of btamas27
Add a Comment

Dito, without any change our nightly build done 12 hours ago was marked 'invalid' with this error while the one done 36 hours ago with the exact same configuration / certificates was processed just fine.

Posted by
janvandenberg04
Up vote reply of janvandenberg04 Down vote reply of janvandenberg04
Add a Comment