ios - when - UITableView inside UIScrollView not receiving first tap after scrollling

uitableview uiscrollview delegate (10)

  1. Drop a UIButton over your UITableViewCell and create the outlet as "btnRowSelect".
  2. In your view controller put this code in cellForRowAtIndexPath

    cell.btnRowSelect.tag = indexPath.row
    cell.btnRowSelect.addTarget(self, action: Selector("rowSelect:"), forControlEvents: .TouchUpInside)
  3. Add this function to your viewController as well-

    func rowSelect (sender:UIButton) {
    // "sendet.tag" give you the selected row 
    // do whatever you want to do in didSelectRowAtIndexPath

This function "rowSelect" will work as didSelectRowAtIndexPath where you get the row"indexPath.row" as "sender.tag"


I am having an issue with a UITableView inside a UIScrollView. When I scroll the external scrollView, the table does not receive the willSelect/didSelect event on the first touch, but it does on the second one. What is even more strange, the cell itself gets the touches and the highlighted state, even when the delegate does not.

Detailed explanation

My view hierarchy:

  - UIScrollView  (outerscroll)
      - Some other views and buttons
      - UITableView (tableView)

Inside the scroll view I have some extra views that get expanded/closed dynamically. The table view needs to get "fixed" on top, together with some other elements of the view, so that is why I created this layout, that allows me to easily move elements in a similar way than Apple recommends by the use of transformations when the scroll happens.

The table View is transformed with a translation effect when the outerscroll moves like this:

- (void)scrollViewDidScroll:(UIScrollView *)scrollView {
    if (scrollView == self.outerScrollView) {

        CGFloat tableOffset = scrollView.contentOffset.y - self.fixedHeaderFrame.origin.y;
        if (tableOffset > 0) {
            self.tableView.contentOffset = CGPointMake(0, tableOffset);
            self.tableView.transform = CGAffineTransformMakeTranslation(0, tableOffset);
        else {
            self.tableView.contentOffset = CGPointMake(0, 0);
            self.tableView.transform = CGAffineTransformIdentity;

        // Other similar transformations are done here, but not involving the table


In my cell, if I implement these methods:

- (void)setSelected:(BOOL)selected {
    [super setSelected:selected];
    if (selected) {

- (void)setHighlighted:(BOOL)highlighted animated:(BOOL)animated
    [super setHighlighted:highlighted animated:animated];
    if (highlighted) {

- (void)touchesBegan:(NSSet *)touches withEvent:(UIEvent *)event {
    [super touchesBegan:touches withEvent:event];

- (void)touchesEnded:(NSSet *)touches withEvent:(UIEvent *)event {
    [super touchesEnded:touches withEvent:event];

- (void)touchesCancelled:(NSSet *)touches withEvent:(UIEvent *)event {
    [super touchesCancelled:touches withEvent:event];

Y can see this output when fails (first tap):

2014-02-10 13:04:40.940 MyOrderApp[5588:70b] highlighted 
2014-02-10 13:04:40.940 MyOrderApp[5588:70b] touchesBegan 
2014-02-10 13:04:40.978 MyOrderApp[5588:70b] touchesEnded

And this one when works (second tap):

2014-02-10 13:05:30.359 MyOrderApp[5588:70b] highlighted 
2014-02-10 13:05:30.360 MyOrderApp[5588:70b] touchesBegan 
2014-02-10 13:05:30.487 MyOrderApp[5588:70b] touchesEnded 
2014-02-10 13:05:30.498 MyOrderApp[5588:70b] expanded

No other frame change, animation or any other view interaction is done between the first and the second tap. Also, only when scrolling large amounts the bug appears, but with scrollings of just a few pixels everything keeps working as expected.

I experimented changing some properties as well, but with no luck. Some of the things I did:

  • Remove userInteractionEnabled from views other than the scroll and table
  • Add a call to setNeedsLayout on the table, scroll and main view when scrollViewDidScroll occurs.
  • Remove the transformations from the table (still happens)

I have seen some comments about the unexpected behaviour of embedding UITableViews inside UIScrollViews but I can not see such a warn in the official documentation by Apple, so I am expecting it to work.

The app is iOS7+ only.


Has anyone experienced similar issues? Why is this and how can I solve it? I think that I could be able to intercept the tap gesture on the cell and pass it with a custom delegate or similar, but I would like the table to receive the proper events and so my UITableViewDelegate receives it as expected.


  • I tried disabling cell reuse as suggested in a comment but it still happens in the same way.

As other answers say you shouldn't put a tableview in a scrollview. A UITableView inherits from UIScrollView anyway so I guess that's where things get confusing. What I always do in this situation is:

1) Subclass UITableViewController and include a property UIView *headView.

2) In the parent UIViewController create all the top stuff in a container UIView

3) Initialise your custom UITableView and add the tableView's view to the view controller full size

[self.view addSubview: self.myTableView.view];

4) Set the headView to be your UIView gubbins

self.tableView.headView = myHeadViewGubbins.

5) In the tableViewController method

-(UIView *)tableView:(UITableView *)tableView viewForHeaderInSection:(NSInteger *)section;


if ( section == 0 ) {
    return self.headView;

Now you have a table view with a bunch of other shizzle at the top.


Gesture recognizers won't work correctly for two embedded scroll views or subclasses.

Try a workaround:

  1. Use transparent, custom, and overlaying everything in cell UIButton with proper tag, or subclass UIButton and add a index path property and overwrite each time in reused cell.

  2. Add this button as a property to your custom cell.

  3. Add target for desired UIControlEvent (one or more) that points to your UITableViewDelegate protocol adopting class.

  4. Disable selecting in IB, and manually manage the selection from code.

This solution requires attention for cases of single/multi selection.

I have the same issue, Then refer to "Nesting Scroll Views" as lxx said.

An example of cross directional scrolling can be found in the Stocks application. The top view is a table view, but the bottom view is a horizontal scroll view configured using paging mode. While two of its three subviews are custom views, the third view (that contains the news articles) is a UITableView (a subclass of UIScrollView) that is a subview of the horizontal scroll view. After you scroll horizontally to the news view, you can then scroll its contents vertically.

It is work

I ran into this same problem and figured out a solution!!

You need to set the delaysTouchesBegan to true on your scrollview so that the scrollview sends its failed scrolled-gesture (i.e. the tap) to its children.

var delaysTouchesBegan: Bool - A Boolean value determining whether the receiver delays sending touches in a begin phase to its view.

When the value of the property is YES, the window suspends delivery of touch objects in the UITouchPhaseBegan phase to the view. If the gesture recognizer subsequently recognizes its gesture, these touch objects are discarded. If the gesture recognizer, however, does not recognize its gesture, the window delivers these objects to the view in a touchesBegan:withEvent: message (and possibly a follow-up touchesMoved:withEvent: message to inform it of the touches’ current locations).

But there's a doesn't work if you do it directly on the scrollview!

// Does NOT work
self.myScrollview.delaysTouchesBegan = true

Apparently this is an iOS bug where setting this property doesn't work (thank you apple). However there's a simple workaround: set the property directly on the scrollview's pan gesture. Sure enough, this worked for me perfectly:

// This works!!
self.myScrollview.panGestureRecognizer.delaysTouchesBegan = true

I would recommend to look for options like not letting your cell to be in highlighted state when you are actually scrolling the outer scroll view which is very easy to handle and is the recommended way. You can do this just by taking a boolean and toggling it in the below method

- (void)scrollViewDidScroll:(UIScrollView *)scrollView 

It seems that your UiTableView doesn't recognize your tap. Did you try to use that :

- (BOOL)gestureRecognizer:(UIPanGestureRecognizer *)gestureRecognizer
shouldRecognizeSimultaneouslyWithGestureRecognizer:(UISwipeGestureRecognizer             *)otherGestureRecognizer
    if ([otherGestureRecognizer.view isKindOfClass:[UITableView class]]) {
        return YES;
    return NO;

Note from apple:

called when the recognition of one of gestureRecognizer or otherGestureRecognizer would be blocked by the other. return YES to allow both to recognize simultaneously. the default implementation returns NO (by default no two gestures can be recognized simultaneously)

note: returning YES is guaranteed to allow simultaneous recognition. returning NO is not guaranteed to prevent simultaneous recognition, as the other gesture's delegate may return YES

Hope that will help.

My mistake was implementing the delegate method:

- (void)tableView:(UITableView *)tableView didDeselectRowAtIndexPath:(NSIndexPath *)indexPath

instead of the one I meant to implement:

- (void)tableView:(UITableView *)tableView didSelectRowAtIndexPath:(NSIndexPath *)indexPath

Hence only being called on the second cell being tapped, because that was when the first cell would be de selected. Stupid mistake made with the help of autocomplete. Just a thought for those of you who may wander here not realizing you've made the same mistake too.

The scrollview is trying to figure out whether the user's intention is to scroll or not, so it's delaying the initial touch on purpose. You can turn this off by setting delaysContentTouches to NO.

leave the inner UITableView's scrollEnabled property set as YES. this lets the inner UITableView know to handle scroll-related touches on the UIScrollView correctly.