从嵌入导航控制器的视图通过Segue向TabBar控制器传值问题

Hey there! Let's work through this data passing headache you're dealing with. It’s totally common to get stuck when view controllers are nested inside navigation and tab bar controllers—those hierarchies can feel like a maze. Let’s break down a few practical solutions tailored exactly to your setup:

This is the most straightforward approach if you’re navigating to the tab bar controller from your source VC. The key is to drill down through the tab bar’s view controllers to get a reference to your DestinationViewController before you navigate.

Example Code (Swift): #

// Inside SourceViewController
// Step 1: Instantiate your tab bar controller (adjust the storyboard ID to match yours)
guard let tabBarVC = storyboard?.instantiateViewController(withIdentifier: "YourTabBarVCID") as? UITabBarController else {
    return
}

// Step 2: Grab the first tab's view controller (your DestinationVC)
if let destinationVC = tabBarVC.viewControllers?.first as? DestinationViewController {
    // Step 3: Assign your data directly to a property on DestinationVC
    destinationVC.userData = "Hi from SourceVC!" // Replace with your actual data
}

// Step 4: Navigate (push since SourceVC is in a navigation stack)
navigationController?.pushViewController(tabBarVC, animated: true)

If your tab bar controller is already the root of your app (and you’re just returning to it from SourceVC), you can grab it from the key window instead:

// Inside SourceViewController
if let tabBarVC = UIApplication.shared.keyWindow?.rootViewController as? UITabBarController {
    if let destinationVC = tabBarVC.viewControllers?.first as? DestinationViewController {
        destinationVC.userData = "Welcome back!"
        // Optional: Switch to the first tab immediately
        tabBarVC.selectedIndex = 0
    }
    // Pop back to the root (or wherever the tab bar lives)
    navigationController?.popToRootViewController(animated: true)
}

Closures are great if you want to avoid tight dependencies between your controllers. You can add a closure property to your custom tab bar controller, then trigger it when the first tab is selected.

Example Code: #

First, create a custom tab bar controller:

class CustomTabBarVC: UITabBarController, UITabBarControllerDelegate {
    // Define a closure to hold the data passing logic
    var passDataToFirstTab: ((String) -> Void)?

    override func viewDidLoad() {
        super.viewDidLoad()
        self.delegate = self // Listen for tab selection changes
    }

    // Trigger the closure when the first tab is selected
    func tabBarController(_ tabBarController: UITabBarController, didSelect viewController: UIViewController) {
        if viewController is DestinationViewController, let passData = passDataToFirstTab {
            passData("Data via closure!")
        }
    }
}

Then in your SourceVC:

// Inside SourceViewController
guard let tabBarVC = storyboard?.instantiateViewController(withIdentifier: "CustomTabBarVC") as? CustomTabBarVC else {
    return
}

// Assign the closure to handle data passing
tabBarVC.passDataToFirstTab = { [weak self] data in
    guard let self = self, let destinationVC = tabBarVC.viewControllers?.first as? DestinationViewController else {
        return
    }
    destinationVC.userData = data
}

navigationController?.pushViewController(tabBarVC, animated: true)

If you don’t want to deal with grabbing controller references at all, Notification Center works well for broadcasting data across your app.

Example Code: #

First, set up the listener in DestinationVC:

class DestinationViewController: UIViewController {
    override func viewDidLoad() {
        super.viewDidLoad()
        // Register to listen for the data notification
        NotificationCenter.default.addObserver(
            self,
            selector: #selector(receiveData(_:)),
            name: NSNotification.Name("PassDataToDestination"),
            object: nil
        )
    }

    @objc private func receiveData(_ notification: Notification) {
        // Extract the data from the notification
        if let data = notification.userInfo?["payload"] as? String {
            self.userData = data
            // Update your UI here
        }
    }

    // Clean up the observer when the VC is deallocated
    deinit {
        NotificationCenter.default.removeObserver(self)
    }
}

Then send the notification from SourceVC:

// Inside SourceViewController
let dataToSend = "Data via notification!"
NotificationCenter.default.post(
    name: NSNotification.Name("PassDataToDestination"),
    object: nil,
    userInfo: ["payload": dataToSend]
)

// Navigate back to the tab bar
navigationController?.popToRootViewController(animated: true)

For quick, temporary data passing, a singleton data manager can work. Just be careful not to overuse this (it can lead to tight coupling if misused).

Example Code: #

First, create the singleton:

class DataStore {
    static let shared = DataStore()
    var tempData: String? // Store your data here
    private init() {} // Prevent external instantiation
}

Then in SourceVC:

// Inside SourceViewController
DataStore.shared.tempData = "Data via singleton!"
navigationController?.popToRootViewController(animated: true)

And in DestinationVC:

class DestinationViewController: UIViewController {
    override func viewWillAppear(_ animated: Bool) {
        super.viewWillAppear(animated)
        if let data = DataStore.shared.tempData {
            self.userData = data
            DataStore.shared.tempData = nil // Clear after use to avoid stale data
        }
    }
}

Quick Recommendations: #

• Use direct assignment if you’re navigating directly to the tab bar controller and need immediate data passing.
• Use closures if you want loose coupling and need to trigger data passing when the tab is selected.
• Use Notification Center for cross-app, one-way data broadcasting.
• Use singletons only for small, temporary data that doesn’t need to persist.

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