I'm seeing the same behavior on Big Sur but the Catalina build is working for me.

I am seeing the same behavior.

I was able to get it to work when I logged in to a test account created in Connect. It didn't work when using my real id. Also, you may need to do this:   #if targetEnvironment(macCatalyst)     if !FileManager.default.fileExists(atPath:Bundle.main.appStoreReceiptURL.path) {         exit(173);     } #endif I remember it was necessary to force a mac app to download a receipt from the store. Once the receipt is downloaded, the app will restart. Best, jaime

I have been seeing these errors, as well, in my catalyst app. I had been ignoring them up to this point. Unfortunately, it seems to be preventing the app from running on the Silicon. It produces a fault and the app will fail to start. I have read that it is produced from older code that was generated before the sandbox. How can one go about finding the code so that it can be upgraded? Best, Jaime

vscpaiva, Are you seeing production receipts with "download_id": 9999 as indicated in your message? I have seen a number of receipts like this as well and am wondering if they are indeed valid. The documentation leads me to believe it is supposed to be a unique identifier. Thanks, Jaime

Did you ever find the answer to this question? I have been wondering the same thing. I don't believe it is possible because it appears as though you have to use the original transaction id in in-app purchases to link two devices. I also am seeing a lot of receipts with a download_id = '9999', so they don't event appear to be unique. I just don't know if this is some sort of scam, however. Best, Jaime

Any possibility that we could see the code used in the testing demo? I would love to see more of those test cases. I'm also curious how you created an SKProduct for use in creating a swiftui preview. If I fetch one via the StoreKit api, the preview fails since it times out. What am I missing? Thanks, Jaime