I'm very happy to hear this! Glad it's helping you.

Thanks Frank!

I am very happy to hear this! Thanks for watching :)

Thanks Drew!

Haha thanks for the comment Dzulqarnain

Wow! Thanks for the support Felix. I'm happy to help. In the next section of the course we will jump into downloading data from the internet, which should be even more exciting than this :)

Thanks for watching beader chen! 🥳

Thanks for the comment Paul! Yea this was one of the harder ones to record because I wanted to get it all into one video. I'm glad it was helpful!

Happy to help!!

Thanks Willow!! :)

So true! CoreData is tough lol even after using it a while I still run into mistakes sometimes 😅😂

😎 Thanks Vlad

It was a long one I had to apologize haha. I wouldn't worry about retaining it all because this isn't as common as the other videos in this playlist. However, if you ever need to implement this, you could probably come back and refresh quickly!

Hey Dave! I am very happy to hear that! The source code for the entire playlist can be found on my Github: github.com/SwiftfulThinking 🥳

You're welcome!

Great questions as always. This is all async code, so timing is definitely a concern. When the app is launched, the CKContainer is automatically set up. We aren't setting that up with these functions. So that app is already connected to CloudKit. The function getiCloudStatus() is then checking if the current user is signed in to their personal Apple ID account on the device. This is required for them to access CloudKit (but CloudKit is technically connected to the app already regardless). This should be the first call and generally will always success - I don't know anyone on an iPhone that isn't signed in to an iCloud account. However, I would have some UI in the app that if this function fails, stop everything else and show a screen that says "you need to sign in to your iCloud account". After that, we can call requestPermission() to check if the current user has granted the app permission to access their personal user information. In production, I would probably sequence these events one-after-another just incase. More practically though, getiCloudStatus() might be something called at app launch (in App Delegate or something) and then getiCloudStatus() might be called during onboarding or something like that.

There are many devs who would argue for Realm over Core Data, I personally choose Core Data every time. It also keeps ur bundle size smaller 🤙

Far from the best, but I'm trying! Thanks for watching :)

Thanks for watching! Realm is also great though. I am just trying to teach the Apple APIs first :)

@@SwiftfulThinking I really like Core Data. After watching your tutorials I see no reason to use Realm anymore , bye bye Realm. Thanks a lot for the good tutorials.

Hi Alexander, this is a great comment. In this video (and in most apps I've seen) CoreData is managed on the main thread, so there are no issues. However, you do need to be careful in a multi-threaded environment. I'm going to add on my a list for a more advanced bootcamp course!

You could probably use the same delete function and just find the items index when you click on it!

Hey Mark, yea the other approach would be updating the array directly. For example, if you are adding a new item, you could 1) add it to CoreData and 2) simply append the item to the array without reloading. I was reloading here to make sure the database is updating correctly. If you do this other approach, you just want to make sure that your CRUD functions are completing successfully. For example, if you add an item to CoreData but it fails to save, you would want to make sure it's not still showing on the UI.

Haha you got this! I know this was a long video

Hey Malbo, that is a great question! I don't think it is possible though. Even if it was, it's probably not something you would want. As the developer, it's pretty important that you have a solid understanding of the CoreData (or any other database) that your users will be using. This way if you need to make updates, you know exactly how their data will be structured. If all of your users had different rules in their CoreData, it would be extremely difficult to update and maintain as you iterate on your app.

Hey Terry, great question. It would actually be outside of the standard MVVM. MVVM is a great starting point but you'll soon realize that there are many more classes and other dependencies that more complex app will require. This Manager class will exist outside of any specific View or ViewModel. In this video, we made it a Singleton which is a global instance of the class. This way multiple ViewModels can then reference the same class. In more advanced apps, we would "inject" the class rather than use a Singleton.

@@SwiftfulThinking Thanks Nick! Understood :) Going to check "injecting", sounds like a useful thing!

Hi Usha, yes you can structure your code in whatever way works best for your app. I used a singleton here just to make it simple.

Hey L S, I can't really tell what the issue is from the explanation. You should be able to set up one-to-many and one-to-one relationships though. Maybe you're setting one of them wrong? Using an array when it shouldn't be.. or vise versa?

Great question. It has to do with the way we set up the view hierarchy for the example project. Without it, the ForEach statements aren't being told to refresh. It was just the easiest way to get through this video. When using this in a production app, you will probably have a very different screen and architecture, and you shouldn't have to add the delay. I hope this wasn't too confusing haha

Store the URL to CoreData and save the image to the FileManager or use an image SDK

@@SwiftfulThinking Thank you for your response. I was storing the images in JPEG compression, but it was allocating a very large amount of memory from the core data when the number of items increased. I tried to improve it with the above link, but I'll try to implement it in the way you suggested, since I'm applying the cloud kit and I also need to consider how to store the images in a document file and how to handle if the user deletes them from that path by chance. Thanks for the advice. You are like a god to me as a self-taught developer. I respect you.

It’s on my GitHub @ SwiftfulThinking !

You need to have code statements under the " var body: some View { " line. (such as: ScrollView {}, or VStack() {}, or Button....etc...otherwise the View protocol is not complete. The View has to have something to display.

Hey Bob! Sorry for the delay. Firstly, thanks for the coffees! .... I just cancelled your membership. You should also be able to sign in and manage your account on www.buymeacoffee.com/nicksarno. The memberships should all be cancel at any time 😅 Anyway, cheers!