I'm also having issues with drag session in UICollectionView in MacCatalyst, but I'm on macOS 10.15.7 and Xcode 11. I'm curious to see if this turns out to be bugs in catalyst or maybe some booking keeping we forgot to do to terminate failed drags, which also triggers the bug I'm seeing. My bug is very similar, which is that I have two UICollectionView's and items are dragged from one to the other. Once the user starts a drag which passes over the second collection view but does not end up dropping the item into the 2nd view, subsequent drags start but new index paths are never provided to my delegate methods. I do get call backs that the drag enters the 2nd collection view, but there is no movement of the items aside to provide space for the drops, and when dropSessionDidUpdate is called, the destination index path is always nil. I think whatever is causing your bug may be very closely related to what's causing mine. (And it's extra frustrating because I've spent a year re-writing my mac app in catalyst to provide a better drag & drop experience! and instead it just breaks and never works again.)

"I was not familiar with this "Close windows when quitting an app" setting, but mine is unchecked.I noticed you said "if you have the System Preference "General -> Close Windows when quitting app" set "On" that the system removes the previously saved sessions and creates a new session when starting the app".But you did not say "if you have the System Preference "General -> Close Windows when quitting app" set "off" that the system correctly restores the scenes just like on ios when starting the app". Does it work correctly for you when turn it off? Perhaps I just need to turn mine one and off again.If apple wants to give the user control over whether the documents are automatically re-opened when the user restarts the app, I don't have a problem with that. But I do have a problem with two things: 1) no option to restore documents when re opening an app, and 2) re-opening the blank windows from previously opened documents and never allowing my code to populate those windows with the document contents.I filed a tech support incident over this, giving up and asking dts to fix my app to handle this correctly, because I was tired of delaying features. I sent them my entire code base. They gave up pretty quickly and told me to file a bug against the OS. I have not received any word about the bug.It looks like Catalina's MacCatalyst simply doesn't fully support document-based apps, and that fact just isn't documented anywhere. Or else it's just another huge ios 13/ctaalina bug they haven't got around to fixing yet. At this point, I've competely given up on their fixing it in catalina and I'm just trying to make enough noise for them to fix it in mac os 10.16, because we only have 5 more months to fix all the bugs in that before my app is delayed for yet a third year due to the os not supporting features they've announced.

So, are you saying there is no way to make this determination on device?

It seems like an error on appreviews' part that they don't have a password to their own test account. Do your statements imply they can never test any functionality which uses receipt refreshing?

Found another thread. Will just follow that one instead. https://forums.developer.apple.com/thread/119837