(This should be a reply to the answer from mjcotr. But for some reason the reply does not seem to work as expected.) Thank you, that looks exactly like what I was looking for. I haven't had heard about @NSApplicationDelegateAdaptor before. I'll give it a try! Thanks, Michael

I think I just ran into the a same issue: https://developer.apple.com/forums/thread/660976 So it seems the issue is still in Xcode 12 and Xcode 12.2 beta.

Now logged as FB8714689.

I have encountered pretty much the same issue: https://developer.apple.com/forums/thread/660976 Filed as: FB8714689

Still not working in Xcode 12 Beta 2 :-(

This seems to be related to issues myself and several others are facing. I asked (here: https://developer.apple.com/forums/thread/662553), if anybody has received any official update on that issue, yet. So far it seems nobody did. Frankly I find it worrying, that something quite fundamentally breaks in a new, but not beta framework and it's three month without a fix or at least getting any info (workaround, or even a "hey, we know it's a bug") from Apple. Any communication on this would not only help to get applications working which were finde in iOS13, but also help to decide, if other issues we are seeing (like animations not working anymore in some cases) are related or something new. So far I haven't received any feedback on the feedback I filed (FB8714689). At least I now see that there are "more than 10" similar reports - it seems we're building a community here ;-). And, to end on on a positive note: So far feedback for SwiftUI I gave, was definitely handled way better/faster, than any other feedback I gave.

Just stumbled across a similar, probably the same issue. Items in an HStack, in a ScrollView. Does not scroll at all... Have you filed a feedback already, so I can reference it in my Feedback?

Hi, it seems @FocusedBinding and @FocusedValue can be used for that, though I have not tried it yet. Please see here, where it is discussed: https://developer.apple.com/forums/thread/651748 . (The last entry there by "Frameworks Engineer") Cheers, Michael

@Claude31 The coding works just fine. My question was, if either the coding is not correct (while working fine) or the documentation is probably not correct (or at least unclear). As for your question regarding my usage of private. Here's the whole paragraph from the documentation - https://developer.apple.com/documentation/swiftui/state (emphasis added). You should only access a state property from inside the view’s body, or from methods called by it. For this reason, declare your state properties as private, to prevent clients of your view from accessing them. It is safe to mutate state properties from any thread. Cheers.

@Claude31 it works with or without the private keyword. My initial question was regarding the correctness of the documentation. I am accessing a @State property outside of a view's body, whereas the documentation states: only access a state property from inside the view’s body Cheers, Michael

If your data is local, then using CoreData might be an option. Then you'd have only one model. If your data resides on a remote server/database, then you'd have a local (Swift)UI model, plus the remote data model. In that case you'd need to write the code to manage loading the proper data from remote into your local UI model. Here you have to be careful, that the remote data is the "source of truth", not the data in your local UI model. One way to handle this would be to only update the remote data model and then load/update the UI model (and never modify the UI model other than from the remote model).

Rearranging the coding a bit (moved coding into a function), it crashes now with this stack (see screenshot). Which leaves me clueless as well ;-).

At least it's good not to be alone ;-). Filed as FB9487340. The simplest example I found, was just having a TextField and tapping on it after a reset of the simulator. Once the keyboard appears and shows the "swipe to type" instructions the crash occurs. The reset of the simulator is necessary so that the "swipe to type" instructions appear, which seem to be the causing the crash in that case.

It only does not work, if the data is stored on iCloud Drive. If it is copied over locally on the iPad it works. So the real question is: How do I make it work on iCloud Drive as well...

Ok, I found the issue (in case anyone with similar issues stumbles across this thread): If you use Set as the type of the relationship property in the NSManagedObject derived class, the above described behavior occurs. Stick with the good old NSSet and it works as expected.