Databases
StackOverflow2013
Postsdbo
POiOS: Tapping on UITableView does not call didSelectRowAtIndexPath
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POiOS: Tapping on UITableView does not call didSelectRowAtIndexPath
    primarykey
    data
    text
    <p>My app uses a <code>UITableView</code> with a <code>UINavigationController</code> to show a more detailed view when a row of the table is tapped - the basic drill-down routine.</p> <p>When I tap on a row, it is highlighted, but the delegate methods <code>tableView:willSelectRowAtIndexPath:</code> or <code>tableView:didSelectRowAtIndexPath:</code> are not called (verified using debugger).</p> <p>Now here's the weird part: </p> <ol> <li><p>There are some other table views in the app (they don't drill down) and none of them exhibit the issue.</p></li> <li><p>If I tap the row rapidly and repeatedly, after many tries (10 - 20 is normal), <code>tableView:willSelectRowAtIndexPath:</code> and <code>tableView:didSelectRowAtIndexPath:</code> <strong>are</strong> called and processing continues normally.</p></li> <li><p>The problem occurs <em>only</em> on an (any, actually) iPad running iOS 6. It works fine with iPads running iOS 5, or with any iPhone running any iOS version, 6. It also works with the iPad simulator using iOS 5 or 6.</p></li> </ol> <p>So it seems that something is receiving the tap before the delegate methods are called. But what?</p> <p>I not using any <code>UITapGestureRecognizer</code>, so <a href="https://stackoverflow.com/questions/8952688/didselectrowatindexpath-not-being-called">that is not the issue</a>. I am not using multiple <code>UITableViewControllers</code> for the table, so <a href="https://stackoverflow.com/questions/2305781/iphone-didselectrowatindexpath-not-invoked">this is also not the issue</a>.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USAnton Meyer
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POiOS: Tapping on UITableView does not call didSelectRowAtIndexPath
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POiOS: Tapping on UITableView does not call didSelectRowAtIndexPath
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POiOS: Tapping on UITableView does not call didSelectRowAtIndexPath
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCheck these things: 1. Confirm the you are the delegate. 2. Does the cells contain any other view? Possibly a UIScrollView or any of it's descendants? 3. Are you running anything very demanding on the main thread?
      singulars
      1. POiOS: Tapping on UITableView does not call didSelectRowAtIndexPath
      1. USABeanSits
    2. CO1. Yes, I am definitely the delegate. 2. Some of the cells contain a UIImageView (with user interaction disabled), the rest contain just the usual UILabel. 3. No, the app is idling.
      singulars
      1. POiOS: Tapping on UITableView does not call didSelectRowAtIndexPath
      1. USAnton Meyer
    3. COHave you done any kind of override of the main UIWindow?
      singulars
      1. POiOS: Tapping on UITableView does not call didSelectRowAtIndexPath
      1. USMike M
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload