How to Resolve the Issue of -didSelectRowAtIndexPath: Not Being Called in iOS Development

How to Resolve the Issue of -didSelectRowAtIndexPath: Not Being Called in iOS Development

6 June 2024 Stephan Petzl Leave a comment Tech-Help

Encountering issues with -didSelectRowAtIndexPath: not being called in your iOS application can be frustrating. This method is essential for handling row selection in a UITableView, and when it doesn’t work, it can significantly affect the user experience. Below, we explore several common reasons for this issue and provide solutions to help you get back on track.

Common Causes and Solutions

1. Method Name Mismatch

Double-check the method name. It’s easy to mistakenly implement -tableView:didDeselectRowAtIndexPath: instead of -tableView:didSelectRowAtIndexPath:. This simple error can cause the selection handler not to be called.

2. Selection Setting

Ensure that the allowsSelection property of your UITableView is set to YES. This can be done programmatically:

tableView.allowsSelection = YES;

Also, verify that the selection type is set correctly in Interface Builder. It should be set to “Single Selection” instead of “No Selection”.

3. UITapGestureRecognizer Interference

If you have a UITapGestureRecognizer added to your view, it might be intercepting the touch events. To prevent this, ensure that the gesture recognizer does not cancel touches in the view:

let tap = UITapGestureRecognizer(target: self, action: #selector(dismissKeyboard))
tap.cancelsTouchesInView = false

4. Delegate and DataSource Settings

Make sure that your view controller is set as the delegate and data source of the UITableView:

self.tableView.delegate = self;
self.tableView.dataSource = self;

5. Editing Mode

If your UITableView is in editing mode, you need to set allowsSelectionDuringEditing to YES:

tableView.allowsSelectionDuringEditing = YES;

Additional Considerations

  • Ensure that no other view within the cell is intercepting the touch events (e.g., a button covering the entire cell).
  • Check for any custom implementations of tableView:willSelectRowAtIndexPath: or tableView:shouldHighlightRowAtIndexPath: that might return nil or NO respectively.


By following the above steps, you should be able to resolve the issue of -didSelectRowAtIndexPath: not being called in your iOS application. Ensuring proper method naming, selection settings, and handling of gesture recognizers are key aspects to check.

For a more streamlined testing process, consider using Repeato, our No-code test automation tool for iOS and Android. With Repeato, you can easily create, run, and maintain automated tests for your apps, allowing you to focus on developing great products. Repeato leverages computer vision and AI, making it particularly fast and efficient, and enabling even non-technical team members to handle test automation.

For more details on how to get started with Repeato, visit our documentation page.

Like this article? there’s more where that came from!