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

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...

+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...?

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, filed a duplicate feedback FB10014055

+1 ... Building my app with macOS 12.3.1 (M1) and Xcode 13.3.1, and no receipt is retrieved after exiting with 173. Tried App Store log out / log in (sandbox and regular account) as well as reboot to no avail.

+1 ... Building my app with macOS 12.3.1 (M1) and Xcode 13.3.1, and no receipt is retrieved after exiting with 173. Tried App Store log out / log in (sandbox and regular account) as well as reboot to no avail.

Is it possible that this bug reappeared? Building my app with macOS 12.3.1 (M1) and Xcode 13.3.1, and no receipt is retrieved after exiting with 173. Tried App Store log out / log in (sandbox and regular account) as well as reboot to no avail...

I just ran into the same issue ... any updates? My app is not fit for a MAS submission, but I'd like to use the notary service to test it internally on several Macs (also from users not part of the dev team).

Feedback (aka RADAR) sent to Apple 1.5 years ago, still "open" and no response (FB7390114). I somehow bypassed the issue as additional file information has been moved from "related items" to extended file attributes, which are accessible from Quick Look.