ITMS-90034: Missing or invalid signature

And so, do you have any informations about this problem ?

Are there any changes about appstore certificate signature verification ?

I'm on XCode 11.3.1 using Mojave 10.14.6.

Thank you.

+1

+1

We had this issue yesterday afternoon. We just resubmitted a new build of the same version, no changes anywhere, and it is now waiting for review having passed the build now. No idea what caused it but may be worth a retry.

Thanks joelloyd-bybox,

hope this has been a temporary issue already resolved (perhaps after the support request I, perhaps also others, have sent).I'll notify here as soon as I receive an official reply from Apple

Same here... Suddenly, the fastlane+Bitrise pipeline stopped working today with errors like

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

It seems to fail randomly. I would suggest resubmitting builds several times. Half of the submitted builds failed for us today.

+1

We just got one build trough now as well! Finally waiting for review. We did not do a single change to this build, just hit rebuild in bitrise (CLI).
Hope this is fixed as well (we also sent a support request, waiting for reply)

+1

Same here

+1

+1

+1

+1

+1

We were running into this issue earlier today with our iOS app. We retried the build again and App Store Connect just finished processed the build, so the issue might be fixed now.

Same here

Same issue here, we are blocked without any information on how to debug this.

Working fine until yesterday, we didn't do any particular change to the signing or to the certificates.

+1

I tried just now 2 times and still failing. Trying 3rd time now.

+1

+1

+1

Deployed 2 test versions to Testflight with no issues, then third test version (15 mins later) failed with that error, no changes in signing

+1

+1

Same here. Worked fine yesterday. No changes today and got this error. Looking at other responses suggests some temporary/random issues Apple's end, so about to try building again.