👨🏻💻 UX Designer, self-employed at NEXT PLANET - small design studio. 👨🏻💻 Indie iOS developer 📱 Creator of: Moons, Numi, Skoro, Wins and Emo. 🎸Guitarist at ZERO and Quadroom 🎨 MA in art 🌱 Vegan
Nothing here yet.
Ben, you should use 0 not 1 to have shortcuts enabled in both modes. I don’t know why did you see this message you posted earlier. Maybe because of macOS 26? Also, this command for changing settings should be posted as one thing. Formatted on blog it looks like separate lines of commands. Also I heard from one person that they needed to grant full disk access to Terminal to make this work - but again the message you posted didn’t look like that’s the case.
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."
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() 😅