NavigationStack and deep links

NavigationStack is driven by a path: an array of Hashable route values (or a NavigationPath). .navigationDestination(for:) maps each route type to a screen. To deep link, parse the URL into routes and set the path. Because the path is data, you can save it, restore it and test it.

Use [Route] with an enum when routes are known; NavigationPath when types vary.

Keep the path in a router model so non-view code can navigate.

Make routes Codable to restore navigation after the app is killed.

NavigationSplitView handles iPad and Mac sidebars.

enum Route: Hashable, Codable { case product(Int), settings }

struct RootView: View {
    @State private var path: [Route] = []
    var body: some View {
        NavigationStack(path: $path) {
            HomeView()
                .navigationDestination(for: Route.self) { route in
                    switch route {
                    case .product(let id): ProductView(id: id)
                    case .settings: SettingsView()
                    }
                }
        }
        .onOpenURL { url in
            if let id = Int(url.lastPathComponent), url.host == "product" { path = [.product(id)] }
        }
    }
}

Common mistakes

• Using the deprecated NavigationLink(isActive:).
• Putting navigationDestination inside a lazy list.
• Nesting NavigationStacks.

Seniors treat navigation as state, which makes deep links, restoration and tests straightforward.

Follow-up questions

Think of your answer first, then open the hint.

1. How do you pop to root?

   Show hint

   Set the path to empty.

2. How do you restore state after the app is killed?

   Show hint

   Encode the path's codable representation in SceneStorage.