I have the same problem and I am seeing other related issues in different forums. Moving away from cocoapods is not viable for me right now. Can I still do archive releases from the 14.2 xcode if I download it from the developer portal, I know in the past sometimes you cannot release from those versions and this is holding up getting out updates. Anyone else come up with other fixes for this? It looks to be a symlink issue fo some sort. Maybe removing intermediates or something. I will update back here if I figure anything out.

The issue magically resolved itself when we attempted again yesterday. Appears to have just been a bug on the site.

I apologize, "one of them result in a successful creation" should read "NONE of them result in a successful creation". I don't see a way to edit the question. I also have a screenshot of the error that I can throw up on s3 if anyone is interested in seeing it.

Just to update here as well, Apple did end up updating their criteria in 4.8 as shown here appstorereviewguidelineshistory.com/ and they have removed the word "exclusively" on March 4th. This now makes all apps that offer any third party logins along with their own authentication to be required to implement Apple Sign In. I did not catch this and was just rejected for not having it. Luckily we implemented this just in case, though it will still take some time to get it merged back in and go through QA.

I got them sorted out yesterday. Does seem to build quicker now.

Migrating to the new build system also is requiring a lot of work currently and does not build my project without errors. Is there no plan to fix this for the legacy build system and we should just count on it the legacy build system no longer being supported?

I am having the same issue. There is also no longer a setting in Build settings for "intent class generation language". The custom intent class is never generated. You can tell by looking in your intent definition file and selecting the custom intent, then in the identity inspector, you normally see an arrow in the "Custom Class" field that will show you where the generated file resides. It is gone, so just like that, updating Xcode has stopped all progress as we try to resolve this since we can no longer build the project without tearing out all references to the custom intent. One thing to note, my custom intents were all being generated in Objective C since my project is 11 years old and mostly in Objective C. Anyone having this issue that has them generated in Swift? I was thinking of trying to just rewrite them all in swift. I will update here if I find a work around. Hopefully Apple can respond to this soon and provide some guidance.

My app has been experiencing this same issue since WatchOS6 and iOS13 release. The only solution we are able to give our users is to uninstall from their watch and install it from the watch app store to ensure they have the latest version. I was really hoping that Apple would have fixed this by now.