如何条件修改UINavigationController回退栈，跳过历史页面（无关来源）

Great question! This is a super common scenario when building sequential workflows (like order entry) where you don’t want users to backtrack through completed steps once they’ve moved to the next stage of the flow. Let’s walk through how to implement this cleanly for your specific page structure.

First, let’s map out your pages for clarity:

• Dashboard: Can navigate to Page 2 or 3
• Order Management: Can navigate to Page 3 or 6
• Page 3: Order Entry (start of order flow)
• Page 4: Order Review
• Page 5: Order Confirmation (back should skip 3 & 4)
• Page 6: Order Status (back should skip 5, with 3 & 4 already skipped)

Approach 1: Modify the Stack When Pushing the Target View Controller #

This is the most straightforward method—adjust the navigation stack right as you push the final page of a workflow. It ensures the stack is correct from the moment the user arrives at the page.

Example 1: Push to Order Confirmation (Page 5) #

When navigating from Page 4 to Page 5, filter out Pages 3 and 4 from the existing stack, then add Page 5 to the cleaned-up stack:

// In OrderReviewViewController (Page 4)
let orderConfirmationVC = OrderConfirmationViewController()

// Get current stack and filter out unwanted pages
guard let currentStack = navigationController?.viewControllers else { return }
let filteredStack = currentStack.filter { vc in
    // Exclude Page 3 and 4
    !(vc is OrderEntryViewController || vc is OrderReviewViewController)
}

// Build new stack and set it
var newStack = filteredStack
newStack.append(orderConfirmationVC)
navigationController?.setViewControllers(newStack, animated: true)

Example 2: Push to Order Status (Page 6) #

When navigating from Page 5 to Page 6, filter out Page 5 (since Pages 3 & 4 are already gone from the stack):

// In OrderConfirmationViewController (Page 5)
let orderStatusVC = OrderStatusViewController()

guard let currentStack = navigationController?.viewControllers else { return }
let filteredStack = currentStack.filter { vc in
    !(vc is OrderConfirmationViewController)
}

var newStack = filteredStack
newStack.append(orderStatusVC)
navigationController?.setViewControllers(newStack, animated: true)

Approach 2: Modify the Stack in the Target Page’s viewWillAppear #

Use this if the target page can be reached from multiple sources (e.g., Page 5 might be accessed from a deep link, not just Page 4). This ensures the stack is corrected every time the page loads.

For Order Confirmation (Page 5) #

class OrderConfirmationViewController: UIViewController {
    override func viewWillAppear(_ animated: Bool) {
        super.viewWillAppear(animated)
        guard let navController = navigationController else { return }
        
        // Only modify the stack if Pages 3/4 are present (avoid repeating changes)
        let hasUnwantedPages = navController.viewControllers.contains { vc in
            vc is OrderEntryViewController || vc is OrderReviewViewController
        }
        guard hasUnwantedPages else { return }
        
        // Filter out unwanted pages
        let filteredStack = navController.viewControllers.filter { vc in
            !(vc is OrderEntryViewController || vc is OrderReviewViewController)
        }
        
        // Ensure current page is in the stack
        var newStack = filteredStack
        if !newStack.contains(self) {
            newStack.append(self)
        }
        
        // Update stack without animation to avoid visual glitches
        navController.setViewControllers(newStack, animated: false)
    }
}

For Order Status (Page 6) #

class OrderStatusViewController: UIViewController {
    override func viewWillAppear(_ animated: Bool) {
        super.viewWillAppear(animated)
        guard let navController = navigationController else { return }
        
        let hasUnwantedPage = navController.viewControllers.contains { vc in
            vc is OrderConfirmationViewController
        }
        guard hasUnwantedPage else { return }
        
        let filteredStack = navController.viewControllers.filter { vc in
            !(vc is OrderConfirmationViewController)
        }
        
        var newStack = filteredStack
        if !newStack.contains(self) {
            newStack.append(self)
        }
        
        navController.setViewControllers(newStack, animated: false)
    }
}

Pro Tips for Maintainability #

• Use Page Identifiers: Instead of checking class types directly, add a custom identifier property to your view controllers. This makes the code more flexible if you rename classes later:

  extension UIViewController {
      var pageIdentifier: String? { nil }
  }
  
  class OrderEntryViewController: UIViewController {
      override var pageIdentifier: String? { "orderEntry" }
  }
  
  // Then filter using identifiers:
  let pagesToSkip = ["orderEntry", "orderReview"]
  let filteredStack = currentStack.filter { !pagesToSkip.contains($0.pageIdentifier ?? "") }
  

• Animation Control: Use animated: true when pushing to keep the standard transition animation. Use animated: false when modifying the stack in viewWillAppear to prevent jarring visual changes.
• Validate Stack Integrity: Always ensure the filtered stack includes your root/entry pages (Dashboard or Order Management) to avoid empty or broken navigation stacks.

内容的提问来源于stack exchange，提问作者Mark A. Donohoe