Post not yet marked as solved
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.)
Post not yet marked as solved
"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.
Post not yet marked as solved
So, are you saying there is no way to make this determination on device?
Post not yet marked as solved
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
Post not yet marked as solved
This bug is now in Catalina public release of 10.15.1 and I'm no longer able to use UICollectionViews in Mac Catalyst.I can no longer develop my MacCatalyst app.Come on Apple.
Post not yet marked as solved
I believe if you use scenes, it's not appropriate for your app to stop when the last scene is closed. When you build an "empty sample project", is it using scenes? If not, then I could see how Apple translates that into quitting the app when the window closes. Does your app use scenes? It sounded like it did. A multi-windowed mac app wouldn't quit when all the documents are closed. It would stay open to allow you to do things like open a recent file, or select "New" from the File menu.
Post not yet marked as solved
I tried printing out the discarded session infunc application(_ application: UIApplication, didDiscardSceneSessions sceneSessions: Set<UISceneSession>)and I was able to verify that the scene session associated with my open document before I quit the app was discarded moments after the app re-launches, and that the new scene it creates when the app opens is not the one that was open before.
Post not yet marked as solved
Yes, I filed a bug report in Feedback Assistant.I also downgraded my mac os from the beta to the non-beta version and the exceptions aren't thrown anymore, and my layout looks like I'd expect, and what it looked like before the beta upgrade, and the same as it does on a real iPad. I hope they fix the bug before the next release!
Post not yet marked as solved
Also works fine on an iPad Pro running os 13, so it's gotta be a bug somehow related to macCatalyst.
Post not yet marked as solved
Upgrading to beta 2 didn't help, but it still works fine in the ipad os 13.2 simulator. I'm reporting this as a bug.I had such big hopes for macCatalyst and UICollectionViewCompositionalLayout, but on a weekly basis I can't practically get any work done for the internal crashing bugs.
Post not yet marked as solved
Well, I need the group to grow based on the size of the cell, so absolute sizes aren't an option for me here in this design.I ran it in the iPad OS 13.1 Simulator, and it worked fine. And it worked fine many many times before I upgraded to the beta. So I'm guessing it's a new bug that's worked its way into the catalina beta (I'm downloading beta 2 of 10.15.1 now).
Post not yet marked as solved
Kumulos confirmed they have no direct support for SiwA, but it could technically be accomplished if I spent enough time writing a "Kscript".
Post not yet marked as solved
Sashido says ParseServer added Sign in with Apple support in v 3.5.0
