Swift 5中关闭详情视图控制器时如何刷新根视图控制器的TableView

Hey there! I totally get the frustration when common methods like notifications or direct tableView references don't work—let me walk you through two reliable, straightforward approaches that I use all the time for this exact scenario.

Approach 1: Using Closures (Super Simple for One-off Updates) #

Closures are great because they create a direct, lightweight connection between your detail view and root view without extra boilerplate.

Step 1: Add a Closure Property to Your Detail View Controller #

In your detail view controller class, define an optional closure that will trigger the refresh:

class DetailViewController: UIViewController {
    // Define the closure property
    var onDataUpdated: (() -> Void)?

    // ... rest of your detail view code
}

Step 2: Trigger the Closure When Data Changes #

Whenever you need to refresh the root tableView (like after saving edits or deleting an item), call the closure:

// Example: After saving changes in detail view
@IBAction func saveButtonTapped(_ sender: UIButton) {
    // Save your data here...
    
    // Trigger the refresh closure
    onDataUpdated?()
    
    // Pop back to root view
    navigationController?.popViewController(animated: true)
}

Step 3: Assign the Closure in Your Root View Controller #

When you're presenting or pushing the detail view from your root view controller, set the closure to reload the tableView. Don't forget to use [weak self] to avoid memory leaks!

class RootTableViewController: UITableViewController {
    // ... your root view code
    
    func navigateToDetailView() {
        let detailVC = storyboard?.instantiateViewController(withIdentifier: "DetailViewController") as! DetailViewController
        
        // Assign the closure to reload tableView
        detailVC.onDataUpdated = { [weak self] in
            self?.tableView.reloadData()
        }
        
        navigationController?.pushViewController(detailVC, animated: true)
    }
}

Approach 2: Using Delegation (Great for Reusable/Complex Flows) #

Delegation is the standard iOS pattern for this kind of communication, perfect if you need the detail view to communicate multiple types of events to the root.

Step 1: Define a Delegate Protocol #

Create a protocol in your detail view controller to define the refresh method:

protocol DetailViewControllerDelegate: AnyObject {
    func didFinishUpdatingData()
}

class DetailViewController: UIViewController {
    // Declare a weak delegate property (weak to prevent retain cycles)
    weak var delegate: DetailViewControllerDelegate?

    // ... rest of your detail view code
}

Step 2: Call the Delegate Method When Needed #

Just like with the closure, trigger the delegate method when your data is ready to be refreshed:

@IBAction func saveButtonTapped(_ sender: UIButton) {
    // Save your data here...
    
    // Notify the delegate to refresh
    delegate?.didFinishUpdatingData()
    
    navigationController?.popViewController(animated: true)
}

Step 3: Conform to the Delegate in Root View Controller #

Make your root view controller adopt the delegate protocol and implement the refresh method:

class RootTableViewController: UITableViewController, DetailViewControllerDelegate {
    // ... your root view code
    
    func navigateToDetailView() {
        let detailVC = storyboard?.instantiateViewController(withIdentifier: "DetailViewController") as! DetailViewController
        
        // Set the delegate
        detailVC.delegate = self
        
        navigationController?.pushViewController(detailVC, animated: true)
    }
    
    // Implement the delegate method
    func didFinishUpdatingData() {
        tableView.reloadData()
    }
}

Why Your Previous Methods Might Have Failed #

• Notifications: Common issues include misspelled notification names, forgetting to remove observers (leading to crashes or no response), or the observer being deallocated before the notification is sent.
• Direct TableView Reference: Holding a strong reference to the root's tableView can create retain cycles, and if the root view is deallocated (unlikely in a navigation stack, but possible), the tableView reference becomes invalid.

Either of the two methods above should work smoothly—pick the one that fits your use case best!

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