4 months and one Xcode version (12.4) later, and still no fix...

But you have mentioned that you have a bypass idea: to put string into clipboard and pronounce it. Does it work? And how to achieve it? Actually this topic has dropped from my todos - mostly because I didn't see any proper way forward. The idea via clipboard would require the user to set up a specific two-step workflow to (1.) run my app and propagate the clipboard and (2.) read its content via a factory action. I don't feel this is a viable solution. Is anybody able to have Siri just speak a text provided by an app extension? It still looks like I'm missing a point... Mattes

The issue of not reading intent results was fixed by Apple with iOS 14.5 - or earlier as I didn't check for quite a time. No code change done...

WTF! I just rechecked on my iPhone running iOS 14.5 and ... it just works as intended (and had with iOS 14): Obviously Apple had introduced some bug with the major iOS update which has been resolved, now. Unfortunately I never found a corresponding information in the change logs. - https://support.apple.com/en-us/HT211808/ I'm a happy camper, again...

The issue of not reading intent results was fixed by Apple with iOS 14.5 - or earlier as I didn't check for quite a time. No code change done...

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.

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

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

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

+1, filed a duplicate feedback FB10014055

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.