在UICollectionView中嵌套UITableView时滚动出现内容上跳问题

Hey Kirti, I’ve dealt with exactly this nested scroll view jump issue before—super frustrating, right? Let’s break down why it’s happening and how to fix it step by step.

The Root Cause #

The main culprit here is UICollectionView cell reuse combined with unmanaged UITableView scroll positions. When you swipe to a new collection view cell, the old cell gets recycled, and the new one (or a reused one) doesn’t remember where the nested table view was scrolled to. On top of that, auto-layout ambiguities or system-adjusted content insets can amplify this jump behavior.

1. Save & Restore UITableView Scroll Positions #

This is the most critical fix. You need to track each collection view cell’s table view offset individually:

• First, add a property to your view controller to store offsets:

  private var tableViewScrollOffsets: [IndexPath: CGPoint] = [:]
  

• When a collection view cell is about to appear, restore its table view’s scroll position:

  func collectionView(_ collectionView: UICollectionView, willDisplay cell: UICollectionViewCell, forItemAt indexPath: IndexPath) {
      guard let customCell = cell as? YourCollectionCellClass else { return }
      
      // Restore saved offset, or reset to top if none exists
      if let savedOffset = tableViewScrollOffsets[indexPath] {
          customCell.tableView.setContentOffset(savedOffset, animated: false)
      } else {
          customCell.tableView.setContentOffset(.zero, animated: false)
      }
  }
  

• When a collection view cell disappears, save its table view’s current offset:

  func collectionView(_ collectionView: UICollectionView, didEndDisplaying cell: UICollectionViewCell, forItemAt indexPath: IndexPath) {
      guard let customCell = cell as? YourCollectionCellClass else { return }
      
      tableViewScrollOffsets[indexPath] = customCell.tableView.contentOffset
  }
  

2. Disable Automatic Content Inset Adjustments #

The system sometimes adjusts contentInset for scroll views (especially around navigation bars or tab bars), which can cause unexpected jumps. Fix this in your custom collection view cell:

override func awakeFromNib() {
    super.awakeFromNib()
    // Prevent system from messing with table view insets
    tableView.contentInsetAdjustmentBehavior = .never
}

3. Stabilize Auto-Layout Constraints #

Ambiguous or late-updating constraints can trigger layout jumps. Double-check your cell’s layout:

• Ensure the UITableView is pinned tight to the cell’s contentView (top, bottom, leading, trailing constraints with priority 1000)
• Force layout updates in the cell’s layoutSubviews() to avoid delayed resizing:

  override func layoutSubviews() {
      super.layoutSubviews()
      // Make sure table view layout is up to date before scrolling
      tableView.layoutIfNeeded()
  }
  

4. Avoid Unnecessary Table View Reloads #

If you’re calling tableView.reloadData() every time the collection view cell displays, it will reset the scroll position to top. Only reload the table view when its underlying data actually changes—not on every cell reuse.

Try these steps in order (start with saving scroll positions, as that’s the most common fix) and your jump issue should disappear. Let me know if you need help adapting any of this to your specific code!

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