“SwiftData inheritance relationship”

Resolved. In the app, all UI elements was created manually and all ViewController inherited from a BaseViewController, including MainMenuViewController. a. the code caused the issue: @interface BaseViewController: AVPlayerViewController b. modified code: @interface BaseViewController: UIViewController Why the base ViewController inherited from AVPlayerViewController, because there's a VideoViewController that will be used to play video. unfortunately, OC don't support multiple inheritance, so I have to embed the base ViewController's functions into VideoViewController instead of inheritance. It's an issue caused by not being careful enough when modifying code.

Now I started facing another problem with pagination: next url is invalid. Get: https://api.appstoreconnect.apple.com/v1/analyticsReportRequests/{id}/relationships/reports?cursor=Mg Error: { errors: [ { id: 56e0cfab-4e86-4e4b-9a12-d76277ad9f94, status: 400, code: PARAMETER_ERROR.INVALID, title: A parameter has an invalid value, detail: 'Mg' is not a valid cursor for this request, source: { parameter: cursor } } ] }

Do you have a minimal sample with detailed steps that reproduce the issue? The way you defined the relationship looks good to me, and so a runnable project may help diagnose the issue. Your post can contain a link to where your test project is hosted. Best, —— Ziqiao Chen  Worldwide Developer Relations.

Yeah, enum RoundAmount is not Codable and so SwiftData doesn't know how to encode / decode MyNumber.rounding. You can fix the issue by making your enum Codable, like below: enum RoundAmount: Int, Codable { case fiveMinute = 5, tenMinute = 10, thirtyMinute = 30 } Best, —— Ziqiao Chen  Worldwide Developer Relations.

When you create a ModelConfiguration, the default value of the cloudKitDatabase attribute .automatic, which tells SwiftData to enable CloudKit synchronization using the primary CloudKit container from the app’s entitlements. That is why you see that SwiftData automatically picks up the CloudKit container, if you configure one in your project, and enables CloudKit integration. If you don't like the default behavior, pass .none when you create the model configuration. Assuming that you use the Xcode template code to trigger the crash, most likely, you will see the following message in your Xcode console: Unresolved error loading container Error Domain=NSCocoaErrorDomain Code=134060 A Core Data error occurred. UserInfo={NSLocalizedFailureReason=CloudKit integration requires that all attributes be optional, or have a default value set. The following attributes are marked non-optional but do not have a default value: Item: timestamp} The log makes clear that the failure is triggered because Item:

The stack trace seems to indicate that your code was trying to retrieve the value of an attribute, but the attribute didn't exist in the SwiftData model. The code snippet shows that TrainInfo and StopStation is a to-many relationship, which has nothing wrong. isOrigin and isStarting seem to be an attribute of StopStation. They are not included in your code snippet, and so I can't comment. Overall, the information you provided doesn't seem to be enough to diagnose the issue... Best, —— Ziqiao Chen  Worldwide Developer Relations.

Theoretically I could not assign the relationships in the willMigrate block Yeah, the context passed to willMigrate is tied to the existing store, which doesn't have the knowledge of your new schema, and so trying to persisting an ItemSchemaV2 object, which I believe is a part of the new schema, will fail. You can consider do the data transformation in didMigrate, where the context is tied to the migrated store, which allows you to access the new schema. but afterwards I am not able to tell which list and items belonged together. Would you mind to share why? When didMigrate is called, ItemSchemaV1.Item and ItemSchemaV1.ItemList have been migrated to ItemSchemaV2.Item and ItemSchemaV2.ItemList, and so you can still fetch the item list from ItemSchemaV2.ItemList, update ItemSchemaV2.ItemList.note, and save the change, can't you? Best, —— Ziqiao Chen  Worldwide Developer Relations.

Was just dealing with the same thing, and removing the id: .self from a ForEach I just added seems to have solved it - thanks! As to the reason, my guess is that SwiftUI is holding a Dictionary of every object, using the id: value as the key - SwiftData is likely mutating these objects behind the scenes, to reload data, fault data, etc. That would cause this error to happen. Omitting the id: parameter in the ForEach, or using id: .id would use the stable identifier as the key of the 'hidden' Dictionary, therefore eliminating the issue. All of that makes sense to me, at least - unfortunately, we use id: .self so frequently, that I can almost guarantee that I'll make this mistake again in the future. Would be nice if making this error were impossible, or if Xcode had a way to warn us about it.

I’m also building a health app. How do I handle a situation where the user doesn’t want to grant Health access, but I want my app to be able to still function using local data via SwiftData? How would these two data stores coexist if the user later grants health access?

hello, first my disclaimer...I am very new to Apple products and my knowledge base is minimal. That said, I have immersed myself in an effort to learn all I possibly can about all topics related to being hacked, because I have also been invaded. i will summarize my experiences and offer a nugget or two of gathered wisdom. i believe the invasion (access to my device) was not physical, and i think it began through using information held only by my provider. **Incidentally, in a separate though related research project, and with info gathered specific to corporate ownership, parent-child relationships, patterns found in company formation/agent for process data/physical addresses offered publicly through registration documentation, and probably more that I do not recall right now...I think I know the person who owns, or has financial control of, my cellular carrier. I will add that this person owns and controls many nationally known companies but disconnects himself by using proxy synthetic identities to