Hello,
my builds keep failing in Xcode Cloud at the creation of the archive for tesflight.
I am receiving an email mentioning "ITMS-90035: Invalid Signature"
TMS-90035: Invalid Signature - Code failed to satisfy specified code requirement(s). The file at path “BASELog.app/BASELog” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/support/code-signing.
The thing is the archives which are not intended for testflight not App Store connect are not failing.
I think I have the required distribution certificates (initially they were created by API for Xcode Icloud, I add 3, revoked them and recreated one manually and the other from Xcode directly) :
even though certificats seems ok, in Xcode I see a dev certificate in the managed release
and if I try to force a distribution certificate in the build
I then get the following warning
It looks like my managed profile is not behaving properly, like not embedding a distribution certificate.
I looked on the web for the signing issues, and I have found in other threads an issue with assets having special charsets. I checked on my side, the only thing I see is my app icon is named "icon_v1.png" I assume it shouldn't be an issue. I dont see any special char anywhere else in the sources name.
Anyone has any idea on what is causing those build fails on the archive?