Swift CoreData问题：自定义函数+sectionNameKeyPath无法为TableView分区

Hey there! Let's figure out why your Core Data + NSFetchedResultsController setup isn't creating the multiple sections you're expecting. I've been stuck on this exact problem before, so let's walk through the most common fixes step by step.

1. Double-Check Your Transient sectionIdentifier Setup #

First, let's make sure your transient property is configured correctly—this is where most people slip up:

• Data Model Configuration: Open your .xcdatamodeld file, select your entity, and confirm the sectionIdentifier attribute has the Transient box checked (under the Data Model Inspector). This tells Core Data not to save this property to the persistent store.
• Getter Method Logic: In your NSManagedObject subclass, the sectionIdentifier getter needs to return a unique value for each group you want as a section. For example, if you're grouping by month/year, your getter should look something like this:

  @objc var sectionIdentifier: String? {
      guard let date = self.dateProperty else { return nil }
      let formatter = DateFormatter()
      formatter.dateFormat = "yyyy-MM"
      return formatter.string(from: date)
  }
  

  Pro Tip: Print out sectionIdentifier for a few objects to confirm they're actually returning different values—if all of them return the same string, you'll only get one section!
• Dependent Keys (Critical!): If your sectionIdentifier relies on another property (like dateProperty above), you need to tell Core Data to track changes to that dependency. Either:
  • Add the dependent property name(s) to the Dependent Keys field in the Data Model Inspector for sectionIdentifier (comma-separated if multiple), or
  • Manually trigger KVO notifications in the dependent property's setter:

    @objc var dateProperty: Date? {
        willSet {
            willChangeValue(forKey: "sectionIdentifier")
        }
        didSet {
            didChangeValue(forKey: "sectionIdentifier")
        }
    }
    

  Without this, Core Data won't know when sectionIdentifier needs to update, so your sections won't refresh when the underlying data changes.

2. Verify Your FRC Configuration #

Your NSFetchedResultsController needs to be set up to use the sectionIdentifier correctly:

• Sort Descriptors: Your fetch request must include a sort descriptor for sectionIdentifier first, followed by any other sort criteria. If you skip this, FRC can't group the results properly:

  let sectionSort = NSSortDescriptor(key: "sectionIdentifier", ascending: true)
  let titleSort = NSSortDescriptor(key: "title", ascending: true)
  fetchRequest.sortDescriptors = [sectionSort, titleSort]
  

• Section Key Path: When initializing the FRC, make sure the sectionNameKeyPath parameter is exactly "sectionIdentifier" (match the property name in your entity/subclass):

  let frc = NSFetchedResultsController(
      fetchRequest: fetchRequest,
      managedObjectContext: yourContext,
      sectionNameKeyPath: "sectionIdentifier",
      cacheName: nil
  )
  

• Perform Fetch & Delegate: Don't forget to set the FRC delegate to your view controller and run the fetch (with error handling!):

  frc.delegate = self
  do {
      try frc.performFetch()
  } catch {
      print("Fetch failed: \(error.localizedDescription)")
  }
  

3. Fix Table View Data Source Methods #

Make sure your table view is pulling section/row counts directly from the FRC, not hardcoding values:

• Number of Sections:

  func numberOfSections(in tableView: UITableView) -> Int {
      return frc.sections?.count ?? 0
  }
  

• Rows per Section:

  func tableView(_ tableView: UITableView, numberOfRowsInSection section: Int) -> Int {
      return frc.sections?[section].numberOfObjects ?? 0
  }
  

• Section Headers (Optional):

  func tableView(_ tableView: UITableView, titleForHeaderInSection section: Int) -> String? {
      return frc.sections?[section].name
  }
  

Quick Debugging Tip #

If you're still stuck, add a print statement right after performFetch() to check what sections the FRC is seeing:

print("Fetched sections: \(frc.sections?.map { $0.name } ?? [])")

This will tell you if the FRC is actually grouping results into multiple sections, or if the issue is in how the table view is displaying them.

Give these steps a shot—nine times out of ten, it's a small oversight in one of these areas causing the problem. Let me know if you run into more issues!

内容的提问来源于stack exchange，提问作者Koh