“SwiftData inheritance relationship”

Hey guys,is it OK for a subclass to implement its own delegate protocol? I have a subclass of UIScrollView which needs to respond to events like scrollViewDidEndDecelerating and scrollViewDidScroll. Therefore, I had to set the delegate property to self and implement the delegate methods inside the subclass. Nevertheless, other classes should still be able to receive these events too, as if they were using the superclass. For example, I want my subclass to do something special when the inherited scrollview ends scrolling, though the external delegate still needs to be informed about the event. Instances of the subclass and the subclass itself use the same delegate object/property. Is this even possible and would it be a safe approach or should the delegate used within the subclass get its own, private property? I appreciate any help you can provide!Cheers,Alex 🙂

The 'Designing for CloudKit' section of the iCloud Design Guide states that CloudKit is a service for moving data to and from iCloud and sharing data between users of your app. It’s your responsibility to convert model objects to records that you save using CloudKit, and to fetch changes made by other users and apply those changes to your model objects.Many CloudKit tutorials that I have followed don't make use of model objects. This results in data should the internet become unavailable. What is the best way to model objects and their relationships that fetch from CloudKit?

We want to distribute a non-AppStore-app to our users over MDM (our users happen to be consumers rather than employees). As our users will have enrolled in our MDM service, their devices will already have established a trust relationship with us, so our app will already be trusted. Our app is not coming from the store, so it will not have been reviewed by Apple. A contact of mine told me that if a device has a non-AppStore-app installed, Apple may consider that device’s warranty to be void, and may refuse to repair it under warranty. It seems unlikely to me that that would be the case for enterprise apps delivered over MDM, but I would like to be sure. Can anyone verify that the Apple device warranty will still be valid when the device has a non-AppStore enterprise app delivered over MDM installed on it?

I have an app which during start, is presented with a Table view controller and a navigation bar with an + button.So far i have this working well to the point where i can save and delete or edit these objects added to the table view. Each individual Item in this table view is selectable and acts like a folder to get a better picture.My problem is, how can i work on adding sub data to specific Parent folders?Sort of works like this graphic representation:Folder_one --> item1 item2Folder_two --> item1Folder_three --> item1 item2 item3 item4I managed to save the Folders on the Parent view controller and selecting one of them, would navigate to the selected folder's table view controller where the user is yet presented with another + button to add an item which stores data to that particular folder. The user can add as many as he/she wants but i cannot seem to work my way around or figure it out how it would work.My data model in Core Data is:Entity name: FolderAttributes: 'name' of type String ' tabColo