ITMS-90034: Missing or invalid signature

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.

+1

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

+1

+1

Same here +1

+1

+1

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.

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.

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

Please don’t use

--deep

--deep

If

--deep

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

let myEmail = "eskimo" + "1" + "@apple.com"

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?

+1

+1

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.

Facing the same issue here.

Tried 2 build uploads and got the same error "ITMS-90034: Missing or invalid signature - The bundle '...' at bundle path 'Payload/...' is not signed using an Apple submission certificate.

Same issues here as well. Tried multiple times...

Could the version of XCode be a factor here? I've noticed for our failing IPA the CI was configured to use XCode 11.1. Currently rebuilding using 11.5 in an attempt to see if that's a factor.

Since you all seem to encounter the same issue under the same circumstances I'm under the impression it's a structural issue, but not THAT big otherwise the internet would explode. So there is something else that is common for our cases but not for all of the uploaders of IPAs to Appstore Connect.

it seems that the issue is with multiple provisioning profiles. If one usese one certificate and other uses other this happens. Try updating your profiles to use one single distribution certificate.

The IPA we have an issue with was configured with a provisioning profile with only a single distribution certificate.

+1

Tried a few hours later without any changes to the configuration and the builds successfully uploaded.

+1

+1

i'm stuck as well

some hour later ... now working