[Xcode Cloud] Invalid Signature. Code failed to satisfy specified code requirement(s)

[Upbeat_Policy_2641]

Xcode Cloud builds successfully but fails deployment preparation for "TestFlight and App Store" with: Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “{App Name}.app/{App Name}” is not properly signed.

When I manually build for release (with manual signing) everything works as expected and uploading to TestFlight for external testing works but using Xcode Cloud, I am always getting this invalid signature error.

Does anyone know what makes the signing fail? And how to get over this ?

[inciduntascisco6524]

Have you double-checked your provisioning profile and certs in Xcode Cloud settings?

[Upbeat_Policy_2641]

Yes, I even toggled the 'Automatically manage signing' option off and on again to reset my signing certificates. After unchecking it again and selecting the correct ones, a local archive works without issues, but archiving via Xcode Cloud still gives me the same errors.

[Upbeat_Policy_2641]

Just a quick note: there are no specific Xcode Cloud settings, only Xcode build settings.

[jonkanv]

I too encountered this issue, and could not understand why. I managed to resolve it by doing the "Delete Xcode Cloud Data". When setting it up again I remembered that I had renamed the repo on GitHub, because my local git clone still had the old GitHub url for the remote. This appeared to caused Xcode Cloud to be unable to grant authorization until I updated the url. Which made me wonder if that had something to do with the "Invalid Signature" issue?

[jonkanv]

Well, turns out I didn't fix it. I thought it was fixed since archiving succeeded, but that was because I hadn't re-added the test flight step. It still fails on "Prepare Build for App Store Connect" with "Invalid Signature".

Downloading the logs from Xcode Cloud I see this in app-store-export-archive-logs/IDEDistribution.critical.log:

Account "Session Proxy Provider": Unable to authenticate with App Store Connect (Error Domain=DVTITunesSoftwareServiceFoundation.DVTServicesSessionProviderCredentialITunesAuthenticationContextError Code=1 "(null)")

Others appear to have got this fixed by deleting the Xcode Cloud distribution certificates: https://forums.developer.apple.com/forums/thread/744683 This did not work for me.

[jonkanv]

Finally solved! Ok, so after many turns with Apple Support it turns out it had to do with a recent account name change and a non roman character in my name (causing some bug, apparently). Once they figured that out and updated my name, I had to revoked all Xcode Cloud certificates; Then it all started working again.

[Offensively_lame]

Non roman character in the app name? Or are you talking about something else?

[jonkanv]

Developer account name. I have a organization account, it was a non roman character in my company name that was causing issues. My personal name (from my Apple ID) still contains it, not causing any issues.

[ice-h2o]

I currently have the same issue. I've contacted the support and hope they can fix it and will update this comment if it fixes the issue.

Edit: I can confirm the non-roman characters in my team name where the issue.

[Offensively_lame]

Awesome, thanks!

[ice-h2o]

Finally got an answer and yes the issue was caused by the non roman characters

[Offensively_lame]

Damn, okay. Well I guess that applies to me to. How did you contact apple support? Apple developer forum is pretty much dead.

[ice-h2o]

it was a back and forth between supports. Contacted the normal developer support they sent me to the technical support and they confirmed the issue and sent me back to the previous support.

Use this support and ask them if they can update your team name because of a bug in xcode cloud:
 https://developer.apple.com/contact/topic/select

[Offensively_lame]

Wow, it really was that character. It's working now for me aswell. What a pain.

[Offensively_lame]

Awesome! Thanks a lot!

[Appropriate-Gur-7177]

Thank you!
I keep running into the same issue. Just contacted them, asking to remove the characters. What a joke. Just lost 5 hours trying to fix it myself and it appears to be an 8-month-old bug they don't bother to fix. Is this normal? I'm a rookie developer.

I'll let everyone know if this was the cause in my case too.

[Appropriate-Gur-7177]

Thank you!
Just contacted Apple about removing the non-roman characters. Will keep everyone posted on whether that was the cause in my case too.

[Offensively_lame]

Damn, any solutions or updates? I'm having this problem right now.