Might be related to a potential MAS outage, as I'm also facing issues validating my app (like mentioned here: "Error Analyzing App Version" https://developer.apple.com/forums/thread/705599)

+1 ... Apple development sucks these days: No receipt generation in sandbox after exit(173), no appstoreconnect.apple.com. Apple, that's no way to treat contributors to your platform, where's your QA...?

For me it worked - at least this morning - when I disabled the upload of debug symbols. Had the same error some months back when distributing universal apps (ARM & Intel), but it "disappeared" after some time. Back again...

This can be avoided by disabling the submission of debug symbols ... Had the same issue months ago on my M1, now it's back.

Currently bypassing the issue by commenting out receipt checks. Unfortunately I recently changed IAP processing in my app, and now releasing it is massively delayed as I cannot test properly. What really annoys my is Apple's ignorance with regards to this issue: No official comment in any discussion, no response to my bug report, and the Developer System Status is still reporting everything "green". That sucks...

Working again without any code change at May 18th, 8:15 pm CEST: obviously Apple has fixed the backend, but no official confirmation of the issue, no response on bug reports, no corresponding system status … Apple, please work on your developer community management.

Working again without any code change at May 18th, 8:15 pm CEST: obviously Apple has fixed the backend, but no official confirmation of the issue, no response on bug reports, no corresponding system status … Apple, please work on your developer community management.

Here we go again: Just changed my IAP validation code and the app is reported as damaged after exiting with 173 and no receipt is delivered. Xcode Version 13.4.1 (13F100) on macOS Monterey 12.4 (21F79). Apple, it sucks...!

Thanks for your reply, Rich, really much appreciated! Providing a freemium app I'm fine with removing the receipt validation at launch. IAP processing is handling a missing receipt now gracefully like no purchase (doing nothing), and the "Restore Purchases" option pulls the receipt ... so I'm good for now. Nevertheless it has a smell that the sandbox environment is not acting like production, and testing cannot be done with full code coverage. In addition - as Brigitte mentioned - the exit(173) is still documented as the proposed step when no receipt is present - especially to check for a legit app at launch. DCAppAttestService cannot cover this for existing apps with support of older macOS versions (like mine).

I'm in the same boat ... at least this thread confirms that it's not my code failing (after 2h testing). Any news? I might file a bug report, although I already have a queue of ignored ones...

RADAR filed (FB10874409)...

I have a related issue which just drives me nuts: For all my iOS projects only simulators running iOS 16.4 are listed as Run Destinations ... although I've installed the iOS 13 simulator and corresponding entries are listed under "Devices & Simulators". I've toggled "Show run destination" from "Automatic" to "Always" with no avail. Deployment target is e.g. iOS 13, and I'm running Xcode Version 14.3 (14E222b). As a current bypass I'm booting up the simulator manually and install apps by "xcrun simctl install booted <path to signed .app>" to allow some basic testing, but that's no sustainable solution. Any help is much appreciated! Mattes

I just installed Xcode and the iOS 13.7 simulator on my Intel Mac Mini: After switching the simulator to "show always" it can be selected as a Run Destination and works. Looks like these "older" simulators are not listed on Macs running with Apple Silicon, like my 14" MBP. I'd consider this a bug...

Did you check out the "accepted reply"? Works for me...

My mistake - I hadn't covered an edge case well (NSString operations with paths). Problem solved.