Post not yet marked as solved
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
Post not yet marked as solved
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
Post not yet marked as solved
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
Post not yet marked as solved
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
Post not yet marked as solved
Obviously this code wasn't tested... which I don't understand. I deselected the ordered attribute from within the core data model editor and then had to alter several files to support these unordered relationships. I got it to compile and run. However, when I added a couple of devices to test cloud kit, it failed miserably. Only approximately 20% of the objects showed up on the other devices. I did see a ton of errors, as well.For example:CoreData: warning: CoreData+CloudKit: -[NSCloudKitMirroringDelegate _recoverFromError:withMonitor:](1648): <NSCloudKitMirroringDelegate: 0x6000027328a0> - Recovered from error: <CKError 0x6000018176c0: "Limit Exceeded" (27/1020); "Your request contains 585 items which is more than the maximum number of items in a single request (400)">and these messages on the mac app:2019-07-20 14:31:13.815095-0700 CoreDataCloudKitDemo[26880:3701480] [AXCommon] Unable to broadcast 1001: err 2684354592019-07-20 14:31:13.999978-0700 CoreDataCloudKitDemo[26880:3682834] [AXRuntimeCommon] AX Lookup problem - errorCode:1102 portName:'com.apple.iphone.axserver' PID:0 (It amazed me because I didn't alter the code enough to challenge the synchronizing. Other than redoing the ordered relationships, this was their example!I wasted months of development trying to get iCloud syncing working with Core Data years ago and this doesn't fill me with any sort of confidence to attempt this again.Frustrated...---------------------------------------------------------------------------------------- Update----------------------------------------------------------------------------------------I walked away for an hour and then decided to try the app again. All of the devices did sync back up and all of the objects appeared on each device. I do wish that there was someway to indicate through the gui that the sync is in process and whether there are errors being reported. I don't like the black box mentality but I am willing to give this another try. There is still hope.
