I am having the exact same problem as @derekst991 what is the conclusion to this? Can I trust that after setting up my transaction observer and performing all the correct steps that updatedTransactions should get called in production even though this is failing with the sandbox?

I have statically linked OpenSSL to my MacOS project, listing OpenSSL under Library search paths and Header Search Paths. Whenever I try to run unit tests, I get 'openssl/conf.h' file not found` Is there any solution for this?

This question was asked in the lounges and it was said that this is apparently possible, but no details were shared. Can someone from Apple please answer this??

I have also tried iOS 16.1 and it still doesn't work there either

It looks like the problem was actually to do with my viewModel not getting correctly re-initialized as it should have inside the NavigationSplitView. After fixing that part, this is now working fine.

thanks @gcledat, there is no use of a timer here per se. Similar to the way that we can program a pause time using Text(timerInterval: dateRange, pauseTime: Date().addingTimeInterval(10), I would have thought we could also set an instruction for a specific date by using Task.sleep If that's not possible, it's very sad indeed. It would be nice to trigger a change in a Live Activity, especially knowing full well in advance a change that needs to happen. Probably what should happen, is Apple should provide is with the Timeline paradigm - the same that is used for regular Widgets

I've seen this problem for the longest time, just submitted my feedback - FB11983783

I'm having exactly the same issue, except that my Mac app has a traditional app delegate. Does anyone have any insights for how to resolve for this scenario?

I have been noticing this issue constantly during the development of my macOS app even after doing the migration steps correctly. The sql file seems to occasionally jump back to a previous version for no apparent reason. I've filed a ticket in feedback, got no reply and am pretty much ready to ask for code level support from Apple. Did you by any chance come by this specific issue in your development?

Another question that comes up is that over the course of 4 years we have on occasion had MacOS users that complain that their app keeps crashing and they can't use it anymore, even if they delete the app entirely from their system. We have tried offering the advice to delete residual app files (sqlite and the other CloudKit ones which seem to stick around) For some users, this seems to work and others it doesn't work at all. What do we do about this?

And in the case of complete migration failure, is there a way to rebuild the database, and how would we go about doing that?