I have a SwiftUI app with 3 Core Data entities, Car, CarService and ServiceRecord where Car has many carServices and each CarService has many serviceRecords. Everything is working fine but I'm not sure what's the most common MVVM practice. As you can see in the following example I'm using CoreDataViewModel to fetch data from Core Data and then I pass it around all SwiftUI views, at the moment I don't have a ViewModel for the view's logic (the logic is currently inside of each view) but that's something I would like to incorporate, but I'm not sure what would be the best way to do that. I'm thinking about the two following option... Create a view model for each view (CarViewModel, ServicesViewModel and RecordsViewModel) to handle ONLY the view's logic and leave the existing CoreDataViewModel as is. Create a view model for each view, CarViewModel, ServicesViewModel and RecordsViewModel to handle the logic for each view and move the CoreData quests to each of the view models respectably and basically delete CoreDataViewModel altogether since now the core data related will live inside each view model. Which of the two options above makes more sense for an MVVM app? In general, can someone please share how you usually structure your code when using MVVM + CoreData + SwiftUI? CoreDataManager class CoreDataManager{ static let instance = CoreDataManager() lazy var context: NSManagedObjectContext = { return container.viewContext }() lazy var container: NSPersistentContainer = { return setupContainer() }() func setupContainer()->NSPersistentContainer{ // code to setup container... return container } func save(){ do{ try context.save() }catch let error{ print("Error saving Core Data. \(error.localizedDescription)") } } } CoreDataViewModel class CoreDataViewModel: ObservableObject{ let manager: CoreDataManager @Published var cars: [Car] = [] @Published var carServices: [CarService] = [] @Published var serviceRecords: [ServiceRecord] = [] init(coreDataManager: CoreDataManager = .instance){ self.manager = coreDataManager // getCars() etc. } // CREATIONS func addCar(name:String){} func addService(name:String, cost: Double){} func createRecord(name:String, cost: Double){} // DELETES func deleteCar(){} func deleteCarService(){} func deleteServiceRecord(){} // UPDATES func updateCar(){} func updateService(){} // GETS func getCars(){} func getServices(){} func getRecords(){} func save(){ self.manager.save() } } SwiftUI Views CarsView struct CarsView: View { @StateObject var coreDataViewModel = CoreDataViewModel() var body: some View { NavigationView{ VStack{ List { ForEach(coreDataViewModel.cars) { car in } } } } } } ServicesView struct ServicesView: View { @ObservedObject var coreDataViewModel:CoreDataViewModel var body: some View { NavigationView{ VStack{ List { ForEach(coreDataViewModel.carServices) { service in } } } } } } RecordsView struct RecordsView: View { @ObservedObject var coreDataViewModel: CoreDataViewModel var body: some View { NavigationView{ VStack{ List { ForEach(coreDataViewModel.serviceRecords) { record in } } } } } } Thanks!

Hi all,I know this is may not be the right forum to post questions about Realm but my issue has to do with the nature of how SwiftUI works.Has anyone been able to successfully integrate Realm with SwiftUI, especially deleting records/rows from a SwiftUI List? I have tried a few different things but no matter what I do I get the same error. After reading some related threads I found out that other people have the same issue but I refuse to think that there is no current solution to integrate Realm with SwiftUI.The following code successfully presents all of the items from Realm in a SwiftUI List, I can create new ones and they show up in the List as expected, my issues is when I try to delete records from the List by either manually pressing a button or by left-swiping to delete the selected row, I get an Index is out of bounds error.Here is my code.Realm Model:class Dog: Object { @objc dynamic var name = "" @objc dynamic var age = 0 @objc dynamic var createdAt = NSDate() @objc dynamic var userID = UUID().uuidString override static func primaryKey() -> String? { return "userID" } }SwiftUI Code:class BindableResults: ObservableObject where Element: RealmSwift.RealmCollectionValue { var results: Results private var token: NotificationToken! init(results: Results) { self.results = results lateInit() } func lateInit() { token = results.observe { [weak self] _ in self?.objectWillChange.send() } } deinit { token.invalidate() } } struct DogRow: View { var dog = Dog() var body: some View { HStack { Text(dog.name) Text("\(dog.age)") } } } struct ContentView : View { @ObservedObject var dogs = BindableResults(results: try! Realm().objects(Dog.self)) var body: some View { VStack{ List{ ForEach(dogs.results, id: \.name) { dog in DogRow(dog: dog) }.onDelete(perform: deleteRow ) } Button(action: { try! realm.write { realm.delete(self.dogs.results[0]) } }){ Text("Delete User") } } } private func deleteRow(with indexSet: IndexSet){ indexSet.forEach ({ index in try! realm.write { realm.delete(self.dogs.results[index]) } }) } }ERRORTerminating app due to uncaught exception ‘RLMException’, reason: ‘Index 23 is out of bounds (must be less than 23).’Of course, the 23 changes depending on how many items are in the Realm database, in this case, I had 24 records when I swiped and tapped the delete button.

Now with Dark Mode I have been creating color assets to manage dark mode colors, but sometimes I think of a more semantic name for a certain color after I have used it in multiple places and I was wondering if there is a way to find where a color has been used even if I have to go and manually changed them, I'm not really looking for an automatic solution.Is there a way to rename or find all of the instances where a custom color asset has been used in Xcode?Thanks!

I have an app that uses local notifications and everything is working fine but I'm debating how to handle pending notifications after the user turned off and turned back on notifications for your app. In other words, let's say that a notification is created and it's meant to be triggered on a certain day but the user turns notifications off the day before the trigger date, then he/she deletes the notification from the app (UI) while notifications for your app were turned off and then after a few days later the user turns on notifications for your app again, at that point there may be notifications that the user no longer wants (since he/she deleted them from the UI) and some that have been expired already. How to find pending notifications that were deleted from the UI but not from the notification center in the event described above? FYI - I know how to delete pending notifications and how to compare notifications in the UI vs notifications in the notifications center. What I'm not sure about is when to do the comparison. Is there a way to get notified when the user turned back on notifications for your app so a method can be triggered to find orphan notifications? Thanks!

Hi,I reciently rewrote on of my apps in Swift and the way I did it is I started from scratch creating a brand new project and what I'm trying to do is to upload this new project as a new version of an existing app in the Appstore.Is this possible to do? If yes, what is the process?Thanks

Can someone please explain why the first time I tap on an item from the list, the selectedItem?.name becomes nil? The second time it shows the right item name correctly but not the first time, why?. I was expecting that to have a value even the first time since I'm setting it in the onTapGesture method selectedItem = item. // model struct Item: Identifiable{   var id = UUID()   var name:String } // SwiftUI struct UpdateStateProperty: View {   var items:[Item] = [Item(name: "Oranges"),             Item(name: "Apples"),             Item(name: "Cookies") ]   @State private var presentView = false   @State private var selectedItem: Item?   var body: some View {     List{       ForEach(items){ item in         HStack{           Text(item.name)         }.onTapGesture {           selectedItem = item           presentView.toggle()         }       }     }     .sheet(isPresented: $presentView){       Text("\(selectedItem?.name)" as String)     }   } }

I have a SwiftUI app that uses CloudKit and Core data to sync data between devices. Everything works fine when testing on devices in Xcode but not in production in the App Store. Can someone explain the typical process when deploying an app that uses CoreData + CloudKit? Is there anything that needs to be done in code or in the CloudKit Console before the app is uploaded to the App Store? Again, my issue is that data doesn't sync when trying to sync data between multiple devices in production but works fine when testing in Xcode. Thanks

I have a SwiftUI app where I would like to enable NSPersistentCloudKitContainer to start using CloudKit and be able to sync the content of the app between multiple devices, but I'm not sure how to handle the user experience. Should this be a feature that the user turns On and Off in the app settings screen or does the user expects the syncing mechanism to work by default without having to do anything, can someone please share your experience on how you implemented CloudKit/Sync in your app. Do I need to offer a login mechanism so the user logs in? Should I include an On/Off option so the user decides if they want the sync option or not? In general, can someone be so kind and explain what the user experience should be when an app provides ClouldKit/sync? FYI - I'm not asking how to implement CloudKit sync I already know what it is and how it works. I just need to know what the expedition is from an app the provides that feature. Thanks!

I'm trying to give the user the ability to decide whether they want to sync to CloudKit or not by turning On or Off a Switch located somewhere in the app settings screen but I'm not sure how to do it in SwiftUI. The following code successfully stops the sync to CloudKit by setting the cloud kit container options to nil description.cloudKitContainerOptions = nil. class CoreDataManager{ static let instance = CoreDataManager() let container: NSPersistentCloudKitContainer let context: NSManagedObjectContext init(){ container = NSPersistentCloudKitContainer(name: "CoreDataContainer") guard let description = container.persistentStoreDescriptions.first else{ fatalError("###\(#function): Failed to retrieve a persistent store description.") } description.setOption(true as NSNumber, forKey: NSPersistentHistoryTrackingKey) description.setOption(true as NSNumber, forKey: NSPersistentStoreRemoteChangeNotificationPostOptionKey) description.cloudKitContainerOptions = nil container.loadPersistentStores { (description, error) in if let error = error{ print("Error loading Core Data. \(error)") } } container.viewContext.automaticallyMergesChangesFromParent = true context = container.viewContext } func save(){ do{ try context.save() print("Saved successfully!") }catch let error{ print("Error saving Core Data. \(error.localizedDescription)") } } } What I ultimately want is to be able to control the syncing process with an @AppStore property or some sort of property, something like this... class CoreDataManager{ @AppStorage("iCloudSync") private var iCloudSync = false //missing code... init(){ if !iCloudSync{ description.cloudKitContainerOptions = nil } } //missing code... } But I'm facing a couple of issues, one, I'm getting an error when using the iCloudSync wrapper variable and the second one and the most difficult for me to solve is the fact that I need to make the persistent storage reload when the switch changes from On to Off of vise-versa. Any idea how can I structure my code so I can control the syncing process and be able to reload the persistent storage when the switch changes? By the way and just for reference, here is how I'm using the CoreDataManager class in my view model. class CarViewModel: ObservableObject{ let manager = CoreDataManager.instance @Published var cars: [Car] = [] init(){ getCars() } func addCar(){} func getCars(){} func deleteCar(){} func save(){ self.manager.save() } }

Hi, I have a SwiftUI ProgressBar View that displays the percentage progress based on a percentage-value you enter as a Bindable parameter. The progress percentage-value is calculated by a ReminderHelper class, which takes two Ints as its parameters, totalDays and daysLeft, the values input to the ReminderHelper class come from a Reminder object saved in Core Data. I'm very confused as to how to structure my code to accomplish such of thing due to the poor understanding of how the SwiftUI/Combine, @Binding, @Published, @State, etc. work. Based on the code below, what I'm expecting to see is two reminders, Cut the Grass at 20% and Power Wash Siding at 50%. Again, the two Ints that determine the total percentage progress come from the Reminder object saved in Core Data and the actual total percentage result comes from the RemindersHelper class. Any idea how to accomplish what I describe above? Model: This is saved in Core Data. class Reminder:Identifiable{ var name = "" var totalDays = 0 var daysLeft = 0 init(name:String, totalDays:Int, daysLeft:Int){ self.name = name self.totalDays = totalDays self.daysLeft = daysLeft } } Helper class This needs to be in charge of calculating the total percentage that will be passed to the ProgressBar View with the values coming from the Reminder object saved in Core Data. class ReminderHelper:ObservableObject{ @Published var percentageLeft: Float = 0.80 func calculatePerentageLeft(daysLeft: Int, totalDays:Int)->Float{ percentageLeft = Float(daysLeft / totalDays) return percentageLeft } } Content View: Here I'm calling the calculatePerentageLeft method to prepare the percentageLeft property before presenting the ProgressBar. Which of course is not working. I see an error: Static method 'buildBlock' requires that 'Float' conform to 'View' struct ContentView: View { var reminders = [Reminder(name: "Cut the Grass", totalDays: 50, daysLeft: 10), Reminder(name: "Power Wash Siding", totalDays: 30, daysLeft: 15)] @StateObject var reminderModel = ReminderHelper() var body: some View { List { ForEach(reminders) { reminder in HStack{ Text(reminder.name) reminderModel.calculatePerentageLeft(daysLeft: reminder.daysLeft, totalDays: reminder.totalDays) ProgressBar(progress: reminderModel.percentageLeft) } } } } } ProgressBar View This is the view in charge of drawing and displaying the percentage value. struct ProgressBar: View { @Binding var progress: Float var body: some View { ZStack { Circle() .stroke(lineWidth:5.0) .opacity(0.3) .foregroundColor(Color.orange) Circle() .trim(from: 0.0, to: CGFloat(min(self.progress, 1.0))) .stroke(style: StrokeStyle(lineWidth: 5.0, lineCap: .round, lineJoin: .round)) .foregroundColor(Color.orange) .rotationEffect(Angle(degrees: 270.0)) .animation(.linear, value: progress) VStack{ Text(String(format: "%.0f %%", min(self.progress, 1.0)*100.0)) .font(.caption2) } } } }

Hi, I recently had an issue with one of my production apps that use Core Data and CloudKit where data wasn't syncing between devices, after a little bit of research I found out that the schema in the private CloudKit container needed to be initialized; which I never did. The part I'm still not 100% sure is when to run the initializeCloudKitSchema method after the app has been released to the AppStore. I see that Apple recommends running it when testing by using #if DEBUG, but... do you really want to run it every time you compile in Xcode? Here is how I understand it at this point... App release, call initializeCloudKitSchema() to match schemas between Core Data and CloudKit. Added or deleted an attribute, call initializeCloudKitSchema() to update the CloudKit schema. Renamed an attribute, call initializeCloudKitSchema() to update the CloudKit schema. Etc. If my assumption above is correct, calling the initializeCloudKitSchema() method during development would update the schema in CloudKit before the new app version is released in the AppStore, therefore creating an issue for existing users with previous versions of the app since they will not have the latest code but will be using the latest schema which contains the new attributes. Can someone please share their method of handling schema updates in CloudKit after the app has been released to the AppStore? Code: do { try container.initializeCloudKitSchema() } catch { print(error) }

I have a code that needs to be ran about every year to update some files at the app launch and I'm trying to come up with the best way to do that. What I need to be able to basically force the app to run the code whenever I need to update the files. This is what I came up with that I think would work but I'm not sure if that's the best way. Are there any other options to handle this type of logic? App version 1 - INITIAL RELASE. This code would work as long as I don't add an update. // First launch @main struct SwifUIPlayGroundApp: App { @AppStorage("shouldLoad") var shouldLoad = true init(){ if shouldLoad{ print("Loading...") shouldLoad = false }else{ print("No need to relaod...") } } } App version 2 - UPDATE 1. Here I would need to add a second variable to force the update shouldUpdate. I would also need to change the logic to check for the shouldUpdate instead of the shouldLoad and set the shouldLoad to true to be prepared for future updates. // UPDATE 1 @main struct SwifUIPlayGroundApp: App { @AppStorage("shouldUpdate") var shouldUpdate = true // new @AppStorage("shouldLoad") var shouldLoad = true init(){ if shouldUpdate{ print("Loading...") shouldUpdate = false shouldLoad = true // prepare for next update }else{ print("No need to relaod...") } } } App version 3 - UPDATE 2. Here I would need to change the logic back to check for the shouldLoad instead of the shouldUpdate and set the shouldUpdate to true to be prepared for future updates. // UPDATE 2 @main struct SwifUIPlayGroundApp: App { @AppStorage("shouldUpdate") var shouldUpdate = true @AppStorage("shouldLoad") var shouldLoad = true init(){ if shouldLoad{ print("Loading...") shouldUpdate = true // prepare for next update shouldLoad = false }else{ print("No need to relaod...") } } } App version 4 - UPDATE 3. Repeat what I did in UPDATE 1...

Any idea why if I tap on Field 1 and immediately after I tap on Field 5, Field 5 gets hidden by the keyboard? To replicate my issue, copy and paste the code below, run it in the simulator and make sure the Toggle Software Keybaord is checked, then go and tap on Field 1 and then on Field 5. I tried wrapping the fields in a List and I got the same result. It almost feels like a bug. The issue seems to occur when moving from the regular .default keyboard type to the .decimalPad keyboard. import SwiftUI struct TextFieldScrollingIssue: View {   @State private var testInput:String = ""   @State private var decimalInput:String = ""       var body: some View {     VStack{       Form {         TextField("Field 1", text:$testInput)           .id("Field 1")           .keyboardType(.default)         Spacer()         Spacer()         Spacer()         Spacer()         Spacer()         Spacer()         Section(header: Text("Section 2: ")) {           TextField("Field 2", text:$testInput)             .id("Field 2")             .keyboardType(.decimalPad)                       TextField("Field 3", text:$decimalInput)             .id("Field 3")             .keyboardType(.decimalPad)         }                   Section(header: Text("Section 3: ")) {           TextField("Field 4", text:$testInput)             .id("Field 4")             .keyboardType(.default)                       TextField("Field 5", text:$decimalInput)             .id("Field 5")             .keyboardType(.decimalPad)         }       }     }   } } struct TextFieldScrollingIssue_Previews: PreviewProvider {   static var previews: some View {     TextFieldScrollingIssue()   } }

Hi, I would like to have a better understanding of Dependency Injection, in general, to start using it. Based on the three examples below, can someone please point out what would be the pros and the cons of using one over the other? 1 - What problem could Example 1 cause if I don't do unitest? This is my current method. 2- What method of Dependency Injection is best to adopt, Example 2 ro Example 3? 3- I noticed that Example 2 enforces to provided the dependency object at instantiation time whereas Example 3 does not. Couldn't Example 3 create confusion for the programmer since if you don't provide the dependency object, the code will still compile without any warning if you call a function that relies on a method inside the injected object? Example 1: Without Dependency Injection class Stereo{ func volume(){ print("Adjusting volume...") } } class Car{ var stereo = Stereo() func adjustVolume(){ stereo.volume() } } let car = Car() car.adjustVolume() Example 2: With Dependency Injection class Stereo{ func volume(){ print("Adjusting volume...") } } class Car{ var stereo: Stereo init(stereo: Stereo){ self.stereo = stereo } func adjustVolume(){ stereo.volume() } } let car = Car(stereo: Stereo()) car.adjustVolume() Example 3: With Optional Dependency Injection class Stereo{ func volume(){ print("Adjusting volume...") } } class Car{ var stereo: Stereo? func adjustVolume(){ stereo?.volume() } // this method can be called without injecting Stereo func someOtherFunction(){ print("Calling some other function...") } } let car = Car() car.stereo = Stereo() car.adjustVolume() Thanks

Can someone please shed some light? I have an app that uses Core Data and CloudKit, up until the last version, I was able to sync data between devices but now after I added two new Entities for some reason it stopped syncing between devices. Here is how I did the change: Created a new Core Data container. Added the new Entities and their Attributes Tested the new Entities locally to be able to send the new schema to CloudKit. Went to CloudKit and made sure that the new Entities and Attributes were reflected on the Developent database. Deploy Schema Cahnges. Went to the Production database to make sure the new schema was deployed; and it was, both databases look the same. Testing: Tested in the simulator and with a real device and everything syncs, even the new Entities. If I download the app from the App Store on two different devices they do NOT sync. Based on the procedure I'm describing above, is there any important step I may have missed when doing the migration? I'm not sure if this is related to the syncing issue but after testing a few times, I no longer can turn the iCloud on, I get the following message when I try to turn iCloud Sync On. CoreData: error: CoreData+CloudKit: -[NSCloudKitMirroringDelegate resetAfterError:andKeepContainer:]: <NSCloudKitMirroringDelegate: 0x282c488c0> - resetting internal state after error: Error Domain=NSCocoaErrorDomain Code=134410 "CloudKit setup failed because there is another instance of this persistent store actively syncing with CloudKit in this process." UserInfo={NSURL=file:///var/mobile/Containers/Data/Application/73F19BC7-4538-4098-85C7-484B36192CF3/Library/Application%20Support/CoreDataContainer.sqlite, NSLocalizedFailureReason=CloudKit setup failed because there is another instance of this persistent store actively syncing with CloudKit in this process., NSUnderlyingException=Illegal attempt to register a second handler for activity identifier com.apple.coredata.cloudkit.activity.setup.8D4C04F6-8040-445A-9447-E5646484521} Any idea of what could be wrong and preventing the devices from syncing? Any idea or suggestion is welcome. Thanks