“SwiftData inheritance relationship”

Definitely an issue in xCode 16.3 as it applies to inherited properties and the simulators. I can't diagnose why it's happening, but there are cases where the value shown in the debugger is not what it should be and that causes code to fail. What's crazy is that looking in the debugger at self.inheritedProperty and then expanding self and drilling down to inheritedProperty, the values do not match. The value on the self node is correct. The issue does not occur on a real device and Xcode 16.0 is still solid as it applies to simulators. Personally, I will be avoiding xCode 16.3 until Apple issues an update that addresses a fix for this.

Do you know how much data is expected to be downloaded? If so, you could ensure the view doesn't update until the right amount of data is received and stored. If you don't know the quantity of data, you could add a Bool and toggle it when the data loading starts, then toggle it when the data has finished loading, so the View is only refreshed when the last of the data is stored. Another way would be to disable the UI so the user can't interact with it until the data has finished loading. The UI would update in the background, but the user wouldn't experience a slow UI as they can't interact with it anyway. You could put a partially-transparent View with a ProgressView in it at the top of a ZStack (which would be at the bottom of the ZStack in the code...) and hide it when you're done. I'll show you how I do it below. There's a few ways of doing it, but I don't think there's a built-in way to achieve this. But then, I'm not a genius on SwiftData, so... Using a blocking view: @State private var loading

I am receiving the same errors on Xcode 16.3 (16E140), using SwiftData but only simply types like String and Date with no transformations.

If Wi-Fi is enabled when the sXGP-SIM is implemented, the crash that in step 8 of the [Operation] in the first explanation will occur 100%. Have you looked at exactly what happens when your app launches in that configuration? I don't see how this would change the systems routing for pushes, but I could see it distorting your apps own network logic. Also, how is the app being distributed to the device? I do not that there are extra verification steps for enterprise apps and, in theory, it's possible that issues with that verification process could delay the app launch long enough that callservicesd then terminates the app. my crash log was below. code:0xBAADCA11 explanation: Yes, that's the termination code. My question was what did the rest of the log show? Is there a way to send the logs other than uploading them directly here? You can either file a bug and post the number back here, or you can file a code level support request and send them through email. However, this is what I would generally prefer: If n

Based on your quote and description, I would agree with your interpretation and confusion. But it is important to remember power discrepancies in any relationship. For all but a few developers, Apple holds all the power and can interpret e.g. to mean whatever it wants. I'm curious now. App Review says that they have resolved your issue. What was the resolution? What does e.g. mean in the context of the Apple App Review Guidelines? Does it mean for example or specifically?

Any updates on this? I'm facing the same issue of @Query loading all the data at once. Is there a way to update the UI when a SwiftData model changes without using @Query?

I'm using SwiftData in getTimeline() and I get the same crash

Maybe the underscore in the property name is causing an issue, could you try with a different name? And shouldn't that property be private so you can only access the relationship in one way?