Why does UITableViewCell remain highlighted?

IosUitableviewCocoa Touch

Ios Problem Overview


What would cause a table view cell to remain highlighted after being touched? I click the cell and can see it stays highlighted as a detail view is pushed. Once the detail view is popped, the cell is still highlighted.

Ios Solutions


Solution 1 - Ios

In your didSelectRowAtIndexPath you need to call deselectRowAtIndexPath to deselect the cell.

So whatever else you are doing in didSelectRowAtIndexPath you just have it call deselectRowAtIndexPath as well.

- (void)tableView:(UITableView *)tableView didSelectRowAtIndexPath:(NSIndexPath *)indexPath {
 // Do some stuff when the row is selected
 [tableView deselectRowAtIndexPath:indexPath animated:YES];
}

Solution 2 - Ios

The most clean way to do it is on viewWillAppear:

- (void)viewWillAppear:(BOOL)animated
{
    [super viewWillAppear:animated];
    // Unselect the selected row if any
    NSIndexPath*    selection = [self.tableView indexPathForSelectedRow];
    if (selection) {
        [self.tableView deselectRowAtIndexPath:selection animated:YES];
    }
}

This way you have the animation of fading out the selection when you return to the controller, as it should be.

Taken from http://forums.macrumors.com/showthread.php?t=577677

Swift version

override func viewDidAppear(_ animated: Bool) {
    super.viewDidAppear(animated)
    
    // deselect the selected row if any
    let selectedRow: IndexPath? = tableView.indexPathForSelectedRow
    if let selectedRowNotNill = selectedRow {
        tableView.deselectRow(at: selectedRowNotNill, animated: true)
    }
}

Solution 3 - Ios

For the Swift users, add this to your code:

func tableView(tableView: UITableView, didSelectRowAtIndexPath indexPath: NSIndexPath) {
    tableView.deselectRowAtIndexPath(indexPath, animated: true)
}

It's paulthenerd's answer but in Swift instead of Obj-C.

Solution 4 - Ios

Did you subclass -(void)viewWillAppear:(BOOL)animated? The selected UITableViewCell won't deselect when you don't call [super viewWillAppear:animated]; in your custom method.

Solution 5 - Ios

Swift 3 Solution

func tableView(_ tableView: UITableView, didSelectRowAt indexPath: IndexPath) {
      tableView.deselectRow(at: indexPath as IndexPath, animated: true)
}

Solution 6 - Ios

If you are using a UITableViewCell, then comment the following line

- (void)setSelected:(BOOL)selected animated:(BOOL)animated
{

 // [super setSelected:selected animated:animated];

}

Hope this helps.

Solution 7 - Ios

Updated with Swift 4

After few experiments, also based of previous answers, I've got the conclusion that the best behaviour can be achieved in 2 ways: (almost identical in practice)

// First Solution: delegate of the table View
func tableView(_ tableView: UITableView, didSelectRowAt indexPath: IndexPath) {
    tableView.deselectRow(at: indexPath, animated: false)
}

// Second Solution: With the life cycle of the view.
override func viewDidDisappear(_ animated: Bool) {
    super.viewDidDisappear(animated)
    
    let selectedRow: IndexPath? = tableView.indexPathForSelectedRow
    if let selectedRow = selectedRow {
        tableView.deselectRow(at: selectedRow, animated: false)
    }
}

I'm personally adopting the first solution, because it's simply more concise. Another possibility, if you need a little animation when you return to your tableView, is to use viewWillAppear:

override func viewWillAppear(_ animated: Bool) {
    super.viewWillAppear(animated)

    let selectedRow: IndexPath? = _view.tableView.indexPathForSelectedRow
    if let selectedRow = selectedRow {
        _view.tableView.deselectRow(at: selectedRow, animated: true)
    }
}

Last but not least, if you're using a UITableViewController, you can also take advantage of the property clearsSelectionOnViewWillAppear.

Solution 8 - Ios

To get the behaviour Kendall Helmstetter Gelner describes in his comment, you likely don't want deselectRowAtIndexPath but rather the clearsSelectionOnViewWillAppear property on your controller. Perhaps this was set to YES by accident?

See the comment in the default Apple template for new UITableViewController subclasses:

- (void)viewDidLoad
{
    [super viewDidLoad];

    // Uncomment the following line to preserve selection between presentations.
    // self.clearsSelectionOnViewWillAppear = NO;
}

Solution 9 - Ios

Swift 5 Solution:

func tableView(tableView: UITableView, didSelectRowAtIndexPath indexPath: NSIndexPath) {
    tableView.deselectRow(at: indexPath as IndexPath, animated: true)
}

Solution 10 - Ios

I was getting this problem as well for my drill-down application. After a viewcontroller, which I'll call VC, returns after pushing another ViewController, the selected cell in VC remained highlighted. In my app, I had created VC to handle the second level (out of three levels) of my drill-down.

The problem in my case is that VC was a UIViewController (that contained a View that contained a TableView). I instead made VC a UITableViewController (that contained a TableView). The UITableViewController class automatically handles the de-highlighting of the table cell after returning from a push. The second answer to the post "Issue with deselectRowAtIndexPath in tableView" gives a more complete answer to this problem.

The problem did not occur for the root viewcontroller because when I created the app as a "Navigation-based App" in XCode, the resulting root viewcontroller was already made to subclass UITableViewController.

Solution 11 - Ios

If none of these work for you, consider this work-around:

Use an unwind segue to call:

@IBAction func unwind_ToTableVC (segue: UIStoryboardSegue) {
    if let index = tableView.indexPathForSelectedRow {
        tableView.deselectRowAtIndexPath(index, animated: true)
    }
}

Why do this? Primarily if you're having trouble getting the deselect code to run at the right time. I had trouble with it not working on the viewWillAppear so the unwind worked a lot better.

Steps:

  1. Write the unwind segue (or paste from above) into your 1st VC (the one with the table)

  2. Go to the 2nd VC. Control-drag from the Cancel/Done/Etc button you're using to dismiss that VC and drag to the Exit Icon at the top.

  3. Select the unwind segue you created in step 1

    Good luck.

Solution 12 - Ios

I am using CoreData so the code that worked for me was a combination of ideas from various answers, in Swift:

override func viewDidAppear(_ animated: Bool) {
    if let testSelected = yourTable.indexPathForSelectedRow {
        yourTable.deselectRow(at: testSelected, animated: true)
    }
    super.viewDidAppear(true)
}

Solution 13 - Ios

 func tableView(_ tableView: UITableView, didSelectRowAt indexPath: IndexPath) {
    tableView.deselectRow(at: indexPath as IndexPath, animated: true)
}

Solution 14 - Ios

I've been having the same issue for long time so in case anyone else is struggling:

Take a look at your -tableView: cellForRowAtIndexPath: and see if you are creating cells or using a 'reuse identifier'. If the latter, make sure that your table in IB has a cell with that identifier. If you're not using a reuse Identifier just create a new cell for each row.

This should then give your table the expected 'fade selected row' on appearing.

Solution 15 - Ios

Use this method in UITableViewCell class

- (void)setSelected:(BOOL)selected animated:(BOOL)animated {
  
   // Just comment This line of code
   // [super setSelected:selected animated:animated];        
}

Solution 16 - Ios

For Swift 3: I would prefer it to use in viewDidDisappear

Define:-

    var selectedIndexPath = IndexPath()

In viewDidDisappear:-

    override func viewDidDisappear(_ animated: Bool) {
    yourTableView.deselectRow(at: selectedIndexPath, animated: true)
}

In didSelectRowAtIndexPath:-

    func tableView(_ tableView: UITableView, didSelectRowAtIndexPath indexPath: IndexPath) {
    selectedIndexPath = indexPath
}

Solution 17 - Ios

if the cell is remaining highlighted after touching it, you can call UITabelView method,

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

`[tableView deselectRowAtIndexPath:indexPath animated:YES];`   

}

Or, you can use the following method and modify it according to your requirements,

// MARK: UITableViewDelegate

func tableView(tableView: UITableView, didHighlightRowAtIndexPath indexPath: NSIndexPath) {
  if let cell = tableView.cellForRowAtIndexPath(indexPath) {
     cell.backgroundColor = UIColor.greenColor()
  }
}

func tableView(tableView: UITableView, didUnhighlightRowAtIndexPath indexPath: NSIndexPath) {
  if let cell = tableView.cellForRowAtIndexPath(indexPath) {
     cell.backgroundColor = UIColor.blackColor()
  }
} 

Solution 18 - Ios

Xcode 10, Swift 4

I had this same issue and discovered I left an empty call to viewWillAppear at the bottom of my tableViewController. Once I removed the empty override function the row no longer stayed highlighted upon return to the tableView view.

problem func

override func viewWillAppear(_ animated: Bool) {
  // need to remove this function if not being used.
}

removing empty function solved my problem.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
Question4thSpaceView Question on Stackoverflow
Solution 1 - IospaulthenerdView Answer on Stackoverflow
Solution 2 - IosDanailView Answer on Stackoverflow
Solution 3 - IosRutger HuijsmansView Answer on Stackoverflow
Solution 4 - IosHansPinckaersView Answer on Stackoverflow
Solution 5 - IosOscar FalmerView Answer on Stackoverflow
Solution 6 - IosShantanuView Answer on Stackoverflow
Solution 7 - IosAlessandro FrancucciView Answer on Stackoverflow
Solution 8 - IosDave TeareView Answer on Stackoverflow
Solution 9 - IosZogView Answer on Stackoverflow
Solution 10 - Iosstackoverflowuser2010View Answer on Stackoverflow
Solution 11 - IosDave GView Answer on Stackoverflow
Solution 12 - IosYewzrView Answer on Stackoverflow
Solution 13 - IosMobView Answer on Stackoverflow
Solution 14 - IosLearningAsIGoView Answer on Stackoverflow
Solution 15 - IossunnyView Answer on Stackoverflow
Solution 16 - IosIrshad QureshiView Answer on Stackoverflow
Solution 17 - IosVarsha ShivhareView Answer on Stackoverflow
Solution 18 - IosRobacView Answer on Stackoverflow