trailingSwipeActionsConfiguration gone?

Question

Created Jul ’20

Replies 5

Boosts 0

Views 2.5k

Participants 3

trailingSwipeActionsConfiguration is gone from UIKit in iOS 14 beta 2 (still there in Catalyst).

Any particular reason? Is it going to come back?

Does that mean that there's no way to implement swipe actions in list collection views?

MT

Boost

Answer 1

Lucky7 OP

Jul ’20

Since this was mentioned during WWDC and demoed on iOS 14 (https://developer.apple.com/wwdc20/10026 at 11:40), I can only assume that it's an issue with Beta 2 and that it'll be back in the next beta.

0

Answer 2

bobasdflkjlkdsfj OP

Jul ’20

Ok, so I had this figured out.

This API diff was more useful than the release notes in identifying the change
codeworkshop.net/objc-diff/sdkdiffs/ios/14.0b2/UIKit.html

The property has been moved from UICollectionViewListCell to UICollectionLayoutListConfiguration

public var trailingSwipeActionsConfigurationProvider: UICollectionLayoutListConfiguration.SwipeActionsConfigurationProvider?
public typealias SwipeActionsConfigurationProvider = (IndexPath) -> UISwipeActionsConfiguration?

What's strange is that you now have to depend on IndexPath which I thought was on the way out... Oh well...

All working, but code that was shown in the videos and early blogs are broken now...

0

Answer 3

Lucky7 OP

Jul ’20

How did you manage to use it? Can't figure it out!

0

Answer 4

Lucky7 OP

Jul ’20

Never mind:

Code Block config.trailingSwipeActionsConfigurationProvider = { indexPath in
...
}

0

Answer 5

Frameworks Engineer OP

Apple

Jul ’20

This moved to UICollectionLayoutListConfiguration as a dynamic provider with the same behavior as on UITableView. This should make it easier to port your existing table view code to collection view lists. It also minimizes the risk that was addressed in the video as already mentioned: the index path is only stored for the duration of the swipe and not over the full lifetime of the cell.

To be clear: you should never store the index path in your action handler. This has always been the case for UITableView and still is the case for collection view lists. This can always lead to issues, it just has a lower chance of surfacing as bugs because the duration that the index path is stored is much smaller with the API in beta 2 and the window in which it could become out of date is smaller.

2