didselectrowatindexpath
didSelectRowAtIndexPath: not being called
I have found the answer. I had a UITapGestureRecognizer set for myTableView’s superView. This overrode the selection call. Credit to whoever suggested that that might be it. Your answer was deleted before I could mark it correct. Set the cancelsTouchesInView property to NO on the gesture recogniser to allow the table view to intercept the … Read more
didSelectRowAtIndexPath returns wrong IndexPath
You have implemented didDeselectRowAtIndexPath. It will be fired when the row is no longer selected. When you touch the second row, the first row is no longer selected, so [0, 1] will be shown. When you touch the first row again, the second row is now no longer selected, so [0, 0] will be shown. … Read more
-didSelectRowAtIndexPath: not being called
Just in case someone made the same stupid mistake as I did: Check out if the method name of what you expect of being didSelect may accidentally be gotten didDeselect in some way. It took about two hours for me to find out …
UITableView didSelectRowAtIndexPath: not being called on first tap
Any chance you accidentally typed didDeselectRowAtIndexPath?