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).
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...!
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.
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...
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...
Post not yet marked as solved
+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...?
+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.
Post not yet marked as solved
+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...
Post not yet marked as solved
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).
Post not yet marked as solved
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.
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...
***! 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...
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
