Thanks Quinn. Since you are at Apple.. What is Apple paying these days for great ideas? I have an idea for an App (which isn't an App anymore) I believe is very useful. Since I cannot make it happen without Apple getting directly involved, perhaps an agreement of some type? Or, maybe they provide me the hook I need and the App is still mine? LMK.

You are not alone. I moved my project from an iMac (2017-MacOS 13.6.6) platform, where everything worked as expected, because Apple will no longer update the OS. I moved to my laptop (M1 2020) with MacOS 14.4.1 running Xcode Version 15.3 (15E204a). My project is directed to MacOS minimum 12.4 using Xcode Project Format 13.0. With no changes (except the usual file errors that need correcting after moving a project to a different machine) I get your above mentioned message in my console output window in the editor. With one additional snafu, I am having issues with the Store. SKPaymentQueue.default().restoreCompletedTransactions() is no longer directed into the Observer ( class StoreObserver : NSObject, SKPaymentTransactionObserver ). func paymentQueue(_ queue: SKPaymentQueue, updatedTransactions transactions: [SKPaymentTransaction]) { print("HELLO I AM READY TO PROCESS YOUR REQUEST FOR RESTORE!") .. more code .. Oddly, this executes when the App loads and the Observer is created BUT, refuses to execute upon command instruction by the .restoreCompletedTransactions. Now, I know this little extra I added wasn't part of the original post but, I thought I'd share. Best of luck.

Additionally, I did some digging to find why my restoreCompletedTransactions() was no longer running after moving to the new platform: I implemented the Failure routine for calling restoreCompletedTransactions() ..func paymentQueue(_ queue: SKPaymentQueue, restoreCompletedTransactionsFailedWithError error: any Error) { print("RESTORE FAILED WITH ERROR:(error)") }.. and was returned an error; [Error Domain=NSURLErrorDomain Code=-1005 "The network connection was lost." UserInfo={NSLocalizedDescription=] Funny thing is, this error only occurs using the new platform. I went back to my iMac OS 13.6.7 with Xcode 15.2 and my restoreCompletedTransactions() still runs perfectly.

the original post in this thread [BOOL _NSPersistentUIDeleteItemAtFileURL(NSURL *const __strong) Failed to]. blah blah Running MacOS 14.5 using Xcode 15.4 after /SavedApplicationState/ the new software combination is using /{bundleIdentifier}/ where the older version MacOS 13.x using Xcode 15.2 is using /{Target}/. Maybe something Apple can comment on?

So, how do you get Apple people to pay attention to something in here. I was notified on the Apple website that I cannot submit a request for personal code review until after June 17th. This has been in here for 6 days and no action. Anyone know how long this takes? I have a stub program that demonstrates this problem without any extraneous code. I can consistently reproduce this error condition. It only happens on MacOS 14.x. The code does not produce errors on MacOS 13.6.

Thank you for taking the time to respond. I have found the source of the problem. The crash report indicated a failure to authenticate, which was no surprise since the User was not supposed to be logged in. The fix was to do something in here: "func paymentQueue(_ queue: SKPaymentQueue, restoreCompletedTransactionsFailedWithError error: Error) {}" I had this setup in my SKPaymentTransactionObserver but it didn't do much. I didn't realize a failed login was being returned to the Transaction Observer. In my development and testing I was never able to produce a scenario when this func would actually be called so, I didn't do anything with it. Now, the func is properly wired into the App and it doesn't crash anymore on a login failure.

HI, Thanks for getting back to me on this. I got busy and couldn't dedicate more time to chasing this issue. I simply continued development on the 2017 iMac. I updated the MacOS and Xcode on the MacBook Air over the last year praying for a fix, to no avail. UNTIL NOW. It is now January 2025 and this problem no longer exists. After the newest release of MacOS and Xcode the issue has solved itself. Thanks.