Hi, Rodrigo. Thank you very much for your comment. I am glad to know that my article helped you 😊 As for the NSPersistentCloudKitContainer name... Did you maybe call your container using the "YourAppName" pattern? If so, yes, you need to use the same name in code. I have the following note in my article that explains more about the name of the container. Please let me know if it's still not clear and needs changes. "We set our container as an NSPersistentCloudKitContainer with a name similar to "iCloud.com.yourDomain.YourAppName". One note here: while Apple suggests this naming convention, you can as well use a different one, for example, "iCloud.YourAppName". The most important thing is that this name must match the name of the iCloud container selected in the Signing & Capabilities tab of your app's target."

Amazing results! Keep going! 👏👏👏

Good article. Thanks for writing this 😊 I have 5 apps on the App Store and all of them are vanilla SwiftUI. No MVVM. Never needed it.

Thank you very much, Sebastian! 😀🙏😀

Thank you, Sebastian! 😀 I hope to get closer to your results soon. Thank you for your articles. They inspire and motivate me.

You’re welcome ☺️ I am happy that you found it useful.

Thank you for writing this article, Daniel! I learned something new. I didn't know about table and tableName! Now my xcloc files will be more organized 😀 Good point about different names for table and tableName parameters. NSLocalizedString also has a tableName parameter from what I am seeing now. So I also don't understand why the SwiftUI team decided to rename it to table for String(), but kept it as tableName for Text() 😅

‪Congratulations on your first article 👏 Thanks for sharing this info. I am sure it will help other iOS developers.

Great list of learning resources. Thank you for sharing. It will help many people a lot 🙏

Great article! 👏👏👏 Thank you very much for this. I am interested in productivity, yet I didn’t know about all the 6 things. Thank you very much for writing this 🙏