UITableView didSelectRowAtIndexPath: not being called on first tap

uitableview cocoa-touch uikit didselectrowatindexpath
Mark Adams picture Mark Adams · Jan 21, 2010 · Viewed 57.7k times · Source

I'm having an issue with UITableView's didSelectRowAtIndexPath.

My table is setup so that when I select row it initializes a new view controller and pushes it.

The first time I tap any row in the table, the method does not get called. Once I select another row, it begins to work as normal.

I have verified this by setting a breakpoint on didSelectRowAtIndexPath. When adding an NSLog to the method I see that when I select the second row that finally pushes the new view controller, I see two log statements appear in the console at the same time.

Any suggestions?

Answer

Ole Begemann picture Ole Begemann · Jan 21, 2010

Any chance you accidentally typed didDeselectRowAtIndexPath?

Related questions

UITableViewCell, show delete button on swipe

How do I get the delete button to show when swiping on a UITableViewCell? The event is never raised and the delete button never appears.

Read More
Using a custom image for a UITableViewCell's accessoryView and having it respond to UITableViewDelegate

I'm using a custom drawn UITableViewCell, including the same for the cell's accessoryView. My setup for the accessoryView happens by the way of something like this: UIImage *accessoryImage = [UIImage imageNamed:@"accessoryDisclosure.png"]; UIImageView *accImageView = [[UIImageView alloc] initWithImage:accessoryImage]; accImageView.userInteractionEnabled = …

Read More
UITableView + Add content offset at top

I need to add some blank space to the top of my UITableView that does not affect the size of the content area. Shifting the content down or adding a blank cell is NOT what I want to do. Instead …

Read More