CODEWITHSUNDEEP
iosswiftuitableview
Kevin Forté
Kevin Forté

Reputation: 73

Having some weird animation bug using TrailingSwipeActionsConfigurationForRowAt to delete cells

I'm trying to simply delete cells with this method of tableView. For some reason, doing so creates this weird animation bug that I can't figure out. Here is my code:

let deleteSubcatAction = UIContextualAction(style: .destructive, title: "Delete") { (action, view, handler) in
    print("Delete Subcategory Action Tapped")
    let subcategory = Global.budget.categories[indexPath.section].subcategories[indexPath.row]
    Global.budget.categories[indexPath.section].subcategories.remove(at: indexPath.row)
    tableView.deleteRows(at: [indexPath], with: .left) }
    
deleteSubcatAction.backgroundColor = .red
let rowConfig = UISwipeActionsConfiguration(actions: [deleteSubcatAction])
return rowConfig

When I drag the cell to the left, I see the delete action as I expect and pressing the action calls the method as it should. However, the cell isn't removed from the table. Instead, the actions stay locked in place and the rest of the content of the cell slides back to the right as if I had released my finger without pressing an action. Then, if I tap elsewhere in my app, the actions minimize back to the right, and the cell simply disappears without any sort of removal animation. Here's a video of the bug I recorded. What's going on here?

Upvotes: 0

Views: 651

Answers (1)

user7192663
user7192663

Reputation:

First thing that pops out is that you aren't calling the completion handler (in your case, the handler property) at the end of your UIContextualAction closure. As in, handler(true).

The second thing is that you aren't doing anything to ensure that the action is properly animated in the table view. The non-intrusive way of doing this (without reloading the entire table view from the data source) is by using:

tableView.beginUpdates()
tableview.endUpdates()

See the API docs for more info.

P.S. Ideally, you should have your data source hooked up to your table view in such a way that the table view reacts to events triggered by observers of your data source, rather than deleting table rows "manually" in response to a UI action.

Upvotes: 2

Related Questions