预选中的UICollectionViewCell允许多选时无法取消选择求助

Hey there! I see you're stuck with pre-selected UICollectionView cells that won't deselect when tapped—let's get this sorted out.

The Root of the Problem #

Your current code manually sets cell.isSelected = true directly in cellForItemAt, but this only updates the cell's UI appearance. It doesn't tell UICollectionView itself that the cell is selected. UICollectionView maintains its own internal list of selected index paths (via indexPathsForSelectedItems), so when a user taps the cell, the system checks its own state—and since it thinks the cell isn't selected, it tries to select it again instead of deselecting it. That's why your UI gets stuck!

Step-by-Step Solution #

1. Let UICollectionView Manage Pre-Selection

Instead of setting cell.isSelected in cellForItemAt, use UICollectionView's built-in method to mark cells as selected when your data loads. For example, add this code in viewDidLoad (or right after your item data is ready):

guard let item = item else { return }

if item.selectionType == .exclusive {
    // For single-select mode
    if let selectedIndex = item.selectedItems?.first {
        let indexPath = IndexPath(item: selectedIndex, section: 0)
        collectionView.selectItem(at: indexPath, animated: false, scrollPosition: [])
    }
} else {
    // For multi-select mode
    item.selectedItems?.forEach { selectedIndex in
        let indexPath = IndexPath(item: selectedIndex, section: 0)
        collectionView.selectItem(at: indexPath, animated: false, scrollPosition: [])
    }
}

This method updates both UICollectionView's internal state and the cell's isSelected property automatically—so your cell's UI will update via your existing isSelected didSet logic.

2. Clean Up cellForItemAt

Remove all the manual cell.isSelected = true code from your cell configuration. Your simplified cellForItemAt should look like this:

public func collectionView(_ collectionView: UICollectionView, cellForItemAt indexPath: IndexPath) -> UICollectionViewCell {
    guard let item = item else { return UICollectionViewCell() }
    
    if let cell = collectionView.dequeueReusableCell(withReuseIdentifier: ModuleSelectorCell.reuseID, for: indexPath) as? ModuleSelectorCell {
        cell.set(item: item.items[indexPath.item])
        // No more manual isSelected settings here!
        return cell
    }
    
    return UICollectionViewCell()
}

3. Verify Selection Mode Settings

Make sure your collection view's selection mode matches your selectionType:

// Set this when your item data loads
if let item = item {
    collectionView.allowsMultipleSelection = (item.selectionType != .exclusive)
}

This ensures single-select mode behaves correctly (only one cell selected at a time) and multi-select allows multiple selections.

4. Sync Your Data Model with Selection Changes (Optional)

If you need to keep your selectedItems array in sync with the collection view's state, implement these delegate methods:

public func collectionView(_ collectionView: UICollectionView, didSelectItemAt indexPath: IndexPath) {
    guard var item = item else { return }
    
    if item.selectionType == .exclusive {
        item.selectedItems = [indexPath.item]
    } else {
        var selectedItems = item.selectedItems ?? []
        selectedItems.append(indexPath.item)
        item.selectedItems = selectedItems
    }
}

public func collectionView(_ collectionView: UICollectionView, didDeselectItemAt indexPath: IndexPath) {
    guard var item = item else { return }
    
    // Only allow deselection in multi-select mode
    if item.selectionType != .exclusive {
        var selectedItems = item.selectedItems ?? []
        selectedItems.removeAll { $0 == indexPath.item }
        item.selectedItems = selectedItems
    }
}

Why This Works #

By letting UICollectionView be the single source of truth for selected states, you ensure the system's internal state and your cell's UI are always in sync. When a user taps a pre-selected cell, the system recognizes it's already in the selected list and triggers a deselection—exactly what you want!

内容的提问来源于stack exchange，提问作者jamiii