Hey there! Let's dig into why your NavigationLink isn't triggering even though Xcode confirms the code's executing. This is a super common gotcha when combining SwiftUI navigation with async operations like CloudKit, so let's break down the most likely culprits and fixes:

1. Your NavigationLink isn’t nested in a Navigation container #

SwiftUI’s navigation system relies entirely on having a NavigationStack (iOS 16+) or NavigationView (older versions) as a parent container for your NavigationLink. If your link is outside this hierarchy, or buried in a sheet/popover that’s not properly linked to the navigation stack, it won’t trigger a jump.

Fix:
Make sure the view containing your NavigationLink (or the state that triggers it) is a direct child of a NavigationStack. For example:

struct YourRootView: View {
    @State private var shouldNavigate = false

    var body: some View {
        // This container is mandatory
        NavigationStack {
            VStack {
                // Your CloudKit-triggered UI here
                Button("Fetch from CloudKit") {
                    fetchFromCloudKit()
                }

                // Hidden link (works for older patterns)
                NavigationLink(isActive: $shouldNavigate) {
                    NextView()
                } label: {
                    EmptyView()
                }
                .hidden()
            }
        }
    }

    private func fetchFromCloudKit() {
        // Your CloudKit logic here
        let container = CKContainer.default()
        container.publicCloudDatabase.perform(/* your query */) { records, error in
            // Always update UI state on main queue!
            DispatchQueue.main.async {
                self.shouldNavigate = true
            }
        }
    }
}

2. You’re updating navigation state off the main thread #

CloudKit callbacks run on a background queue by default. If you modify your @State or @Binding navigation trigger variable directly in this callback, SwiftUI might not detect the state change (since UI updates must happen on the main thread).

Fix:
Wrap all state updates that trigger navigation in DispatchQueue.main.async:

// Inside your CloudKit completion handler
DispatchQueue.main.async {
    self.shouldNavigate = true
    // OR for iOS 16+ NavigationPath:
    self.path.append(NextView())
}

3. You’re using an outdated NavigationLink pattern (iOS 16+) #

If you’re targeting iOS 16 or later, the old NavigationLink(isActive:) pattern can be flaky with async operations. The newer NavigationStack + NavigationPath approach is much more reliable for programmatic navigation.

Fix:
Use a NavigationPath to manage your navigation stack:

struct YourRootView: View {
    @State private var path = NavigationPath() // Tracks navigation stack
    @StateObject private var cloudKitManager = CloudKitManager()

    var body: some View {
        NavigationStack(path: $path) {
            Button("Fetch & Navigate") {
                cloudKitManager.fetchData { success in
                    if success {
                        DispatchQueue.main.async {
                            path.append("nextView") // Append a value to trigger navigation
                        }
                    }
                }
            }
            // Define where to go when the path contains this value
            .navigationDestination(for: String.self) { value in
                if value == "nextView" {
                    NextView()
                }
            }
        }
    }
}

4. Your NavigationLink is conditionally removed from the view hierarchy #

If you’re wrapping your NavigationLink in an if statement that hides it before the CloudKit operation completes, the link won’t exist in the view tree when you try to trigger it.

Fix:
Either keep the NavigationLink in the hierarchy permanently (use .hidden() to hide it visually) or switch to the NavigationPath pattern which doesn’t require a visible link at all.

5. Your navigation state is in the wrong scope #

If your @State variable is defined in a child view that gets reinitialized before the CloudKit operation finishes, the state will reset and the navigation trigger will be lost.

Fix:
Move your navigation state to a parent view or a view model (using @StateObject/@ObservableObject) so it persists for the lifetime of the operation.

• Is there a NavigationStack/NavigationView wrapping your navigation trigger?
• Are you updating navigation state on the main thread?
• Is your NavigationLink always present in the view hierarchy (or are you using NavigationPath)?
• Is your navigation state variable in a persistent scope (not a temporary child view)?

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