Can't upload to AppStore - Invalid Provisioning Signature

same here, how did you fix it?

You are not alone. This suddenly started happening foe us too.

same here XCode Version 13.2

ok so I'm going to bed, i wait that Apple will fix it.

Same issue on my side

ITMS-90165: Invalid Provisioning Profile Signature - The provisioning profile included in the bundle '***' cannot be used to submit apps to the iOS App Store until it has a valid signature from Apple. For more information, visit the iOS Developer Portal.

Same here! No hope. Xcode Version 13.3.1 (13E500a) #ITM-90165 / ITM-90165

Same here with Xcode 13.3.1

Lucky for me, I have another Mac with Xcode 13.3, which didn't yet update. Archiving from that Mac worked without any issue.

I'm on Xcode 13.3 too, but same issue..

Same here! Using Xcode 13.2

I have the same problem XCode 13.2 Yesterday I uploaded but today I can't :/

Same

Same!

happening for me as well

Happening here too. Very frustrating!

I had the same issue. Creating a new Distribution certificate through Xcode allowed me to upload.

I also had the same issue, came to this post from here https://developer.apple.com/forums/thread/681482

I fixed this like @valuedcustomer said, by creating a new distribution certificate through xcode.

+1

Create a new distribution certificate through Xcode. I have just done this and it now works.

Preferences > Accounts > Choose team > Manage certificates > + Apple distribution > Archive and upload

I deleted the Provision Profile from the Apple Developer Portal recreated downloaded the new one and the problem is fixed

I suspect anything that regenerates the provisioning profile will fix this.

If you use a manual profile you can "Edit" the existing provisioning profile at https://developer.apple.com/account/resources/profiles/list. Click the profile, click Edit, then "Save" to regenerate it. You can download and install the profile, or use the Xcode > Preferences > Accounts > Download Manual Profiles. (This is what I did and it worked.)

Deleting and making a new provisioning profile is functionally the same (in this case) as editing an existing one.

Making a new certificate with auto-signing also causes a new provisioning profile to be generated.

Depending on your context - like distributed teams and build servers - some of these are more disruptive than others. Choose wisely!

Update

Seems you don't even need to "Edit" the profile. Just get Xcode to redownload them by clearing out ~/Library/MobileDevice/Provisioning Profiles. See https://twitter.com/hunter/status/1513960632059510784

Problem solved, I can now upload updates to my applications.

Since I couldn't remove the distribution certificate in Xcode, go to: https://developer.apple.com/account/resources/certificates

And delete the certificate, then go into Xcode and create it again and the problem is solved.

Has anyone using fastlane match been able to resolve this issue? We just recreated our distribution cert/profile a month ago and it has worked for several app submission up until today. Recreating the cert/profile in Xcode isn't a (long term) solution for us.

Same here

Solved for me:

1. I deleted all files here ~/Library/MobileDevice/Provisioning Profiles.
2. In Xcode accounts I Downloaded Manual Profiles again

We are using Microsoft AppCenter to build our iOS app and this just started happening for me. I went to the developer portal, edited the profile and re-downloaded it. I then uploaded into appcenter and kicked off another build and everything worked.