TableViewCell关联多ViewController跳转失效及数据传递咨询

Hey there! Let's tackle your two main issues one by one—first getting that cell tap to trigger a segue, then passing data smoothly to the destination view controller.

If your cells are populated but tapping them does nothing, here are the most common things to check:

• Check the UITableView delegate connection: Your view controller needs to conform to UITableViewDelegate, and you have to set tableView.delegate = self (either in viewDidLoad() or via Interface Builder by connecting the delegate outlet from the table view to your VC). Without this, the tableView(_:didSelectRowAt:) method won’t fire at all.
• Verify didSelectRowAt implementation: Double-check that you’ve written this method correctly—even a tiny typo (like misspelling the method name) will break it. Here’s a correct example:

  func tableView(_ tableView: UITableView, didSelectRowAt indexPath: IndexPath) {
      // Trigger your segue or push the VC directly here
      performSegue(withIdentifier: "YourSegueIdentifier", sender: indexPath)
  }
  

• Validate storyboard segue setup:
  • If you’re using a segue from the view controller to the destination VC, make sure it has a unique identifier that matches what you use in performSegue(withIdentifier:).
  • If you dragged the segue directly from the cell to the destination VC, confirm the segue’s identifier is correct, and that neither the cell nor any of its subviews have isUserInteractionEnabled set to false (that would block taps).
• Check for gesture recognizers: If you added any tap gesture recognizers to the cell or its subviews, they might be intercepting the tap before it reaches the table view’s delegate. Make sure those gestures are configured properly (or remove them if they’re unnecessary).

You don’t have to handle data passing separately in every single view controller—there are clean, scalable approaches that work across your app. Let’s cover the most useful methods:

Option 1: Using prepare(for:sender:) (Storyboard Segues) #

This is the standard approach for storyboard-based projects. You pass data right before the segue executes:

First, add public properties to your destination VC to accept the data:

class DestinationViewController: UIViewController {
    // Properties to hold incoming data
    var itemTitle: String?
    var itemImage: UIImage?

    override func viewDidLoad() {
        super.viewDidLoad()
        // Use the data to update your UI
        titleLabel.text = itemTitle
        itemImageView.image = itemImage
    }
}

Then, implement prepare(for:sender:) in your table view controller:

override func prepare(for segue: UIStoryboardSegue, sender: Any?) {
    guard segue.identifier == "YourSegueIdentifier",
          let destinationVC = segue.destination as? DestinationViewController,
          let indexPath = sender as? IndexPath else {
        return
    }

    // Get the data for the selected cell from your data source
    let selectedItem = yourDataSourceArray[indexPath.row]
    // Pass the data to the destination VC
    destinationVC.itemTitle = selectedItem.title
    destinationVC.itemImage = selectedItem.image
}

Option 2: Manual Navigation (Programmatic VCs) #

If you’re creating view controllers programmatically (no storyboards), you can initialize the destination VC and pass data directly before pushing it:

func tableView(_ tableView: UITableView, didSelectRowAt indexPath: IndexPath) {
    let selectedItem = yourDataSourceArray[indexPath.row]
    let destinationVC = DestinationViewController()
    
    // Pass data directly to the VC's properties
    destinationVC.itemTitle = selectedItem.title
    destinationVC.itemImage = selectedItem.image
    
    // Push the VC onto the navigation stack
    navigationController?.pushViewController(destinationVC, animated: true)
}

Option 3: Scalable ViewModel Approach (Clean & Reusable) #

For a more maintainable solution—especially if you have multiple destination VCs or complex data—use a ViewModel to encapsulate all the data a VC needs. This way, you don’t have to add individual properties to every VC:

First, create a ViewModel struct:

struct ItemViewModel {
    let title: String
    let image: UIImage
    // Add any other data fields your VC needs
}

Then, initialize your destination VC with the ViewModel:

class DestinationViewController: UIViewController {
    private let viewModel: ItemViewModel

    // Initialize with the ViewModel (required for programmatic setup)
    init(viewModel: ItemViewModel) {
        self.viewModel = viewModel
        super.init(nibName: nil, bundle: nil)
    }

    // Required for storyboard support (if needed)
    required init?(coder: NSCoder) {
        fatalError("init(coder:) has not been implemented")
    }

    override func viewDidLoad() {
        super.viewDidLoad()
        // Use the ViewModel to populate your UI
        titleLabel.text = viewModel.title
        itemImageView.image = viewModel.image
    }
}

In your table view controller, pass the ViewModel when tapping a cell:

func tableView(_ tableView: UITableView, didSelectRowAt indexPath: IndexPath) {
    let selectedViewModel = yourViewModelArray[indexPath.row]
    let destinationVC = DestinationViewController(viewModel: selectedViewModel)
    navigationController?.pushViewController(destinationVC, animated: true)
}

This approach keeps your code organized, makes it easier to reuse data across VCs, and reduces the chance of bugs from missing properties.

内容的提问来源于stack exchange，提问作者Omar Al-Eisa