TabBarController中NavigationController推送视图控制器无动画问题

Hey there, let's figure out this weird navigation issue you're dealing with! I’ve run into similar cases before when working with nested navigation controllers under a tab bar, so here’s a breakdown of what’s probably going on and how to fix it:

This problem almost always boils down to one of a few things:

• You’re grabbing the wrong UINavigationController instance in your cell tap handler
• The push operation isn’t being executed on the main thread
• You’ve customized the navigation bar’s back button in a way that breaks the system’s interactive swipe-to-go-back gesture

1. Make Sure You’re Using the Correct Navigation Controller #

If your tap logic is inside the collection view cell class (which it shouldn’t be, for separation of concerns), self.navigationController will return nil because cells don’t have a navigation controller reference. Instead, pass the tap event back to your UICollectionViewController to handle the push:

Use a Closure to Pass Tap Events to the Controller #

First, add a closure property to your cell class:

class CustomCollectionViewCell: UICollectionViewCell {
    var onTap: (() -> Void)?

    // Connect this to your cell's tap gesture or button
    @IBAction func cellTapped(_ sender: UIButton) {
        onTap?()
    }
}

Then, in your UICollectionViewController’s cellForItemAt method, assign the closure and handle the push there:

override func collectionView(_ collectionView: UICollectionView, cellForItemAt indexPath: IndexPath) -> UICollectionViewCell {
    let cell = collectionView.dequeueReusableCell(withReuseIdentifier: "YourCellID", for: indexPath) as! CustomCollectionViewCell
    
    cell.onTap = { [weak self] in
        guard let self = self else { return }
        let targetVC = SomeViewController()
        // This uses the correct navigation controller from the collection view controller
        self.navigationController?.pushViewController(targetVC, animated: true)
    }
    
    return cell
}

2. Ensure the Push Runs on the Main Thread #

UI operations must happen on the main thread. If your tap handler is triggered after an async task (like loading data into the cell), wrap the push in a main thread dispatch:

cell.onTap = { [weak self] in
    guard let self = self else { return }
    DispatchQueue.main.async {
        let targetVC = SomeViewController()
        self.navigationController?.pushViewController(targetVC, animated: true)
    }
}

3. Restore the Interactive Swipe-to-Go-Back Gesture #

If the back button appears but you can’t swipe to return, customizing navigationItem.leftBarButtonItem often disables the system’s gesture. Fix this by setting the gesture delegate:

First, add the delegate to your UICollectionViewController:

extension YourCollectionViewController: UIGestureRecognizerDelegate {}

Then, in viewDidLoad, link the gesture delegate and allow it to activate only when there’s more than one controller in the stack:

override func viewDidLoad() {
    super.viewDidLoad()
    navigationController?.interactivePopGestureRecognizer?.delegate = self
}

func gestureRecognizerShouldBegin(_ gestureRecognizer: UIGestureRecognizer) -> Bool {
    // Only allow swipe back if there's more than one VC in the stack
    return navigationController?.viewControllers.count ?? 0 > 1
}

4. Verify Your Navigation Stack Hierarchy #

Before pushing, print the current navigation stack to confirm your UICollectionViewController is actually part of it:

print("Current navigation stack: \(navigationController?.viewControllers ?? [])")

If your collection view controller isn’t listed, double-check your UITabBarController setup: make sure each tab’s root is a UINavigationController, and your UICollectionViewController is set as that navigation controller’s root view controller.

If you’re using custom subclasses of UITabBarController or UINavigationController, make sure you haven’t overridden pushViewController(_:animated:) in a way that skips animations or modifies the stack incorrectly.

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