ios – Authentication Stream: Stopping unauthorized entry with NavigationStack or fullScreenCover or different?

I’m designing a SwiftUI app with two most important views:

• Login View
• Essential View (for logged-in customers)

Necessities

• Customers should log in earlier than accessing the primary app.

Approaches Thought-about

1. NavigationStack with an enum for locations

• Feels unidiomatic to combine authentication logic with navigation.
• With out navigationBarBackButtonHidden, customers can navigate again to a placeholder root view.

2. fullScreenCover over the Essential View

• Prevents again navigation however interferes with onAppear logic in the primary view, which ought to solely run after login.

What’s the idiomatic SwiftUI strategy for dealing with authentication-based navigation? Can this be performed purely in SwiftUI, or is UIKit a greater match?

I’ve seen two approaches which may fulfill my wants, however I’m not certain whether or not they’re idiomatic and even the right method of dealing with this.

Utilizing NavigationStack, together with an Enum for Locations

struct ContentView: View {
    @State non-public var path = [Destination]()
    @State non-public var isLoggedIn = true
    var physique: some View {
        NavigationStack(path: $path) {
            ProgressView("Placeholder till onAppear pushes the correct vacation spot onto the stack")
                .navigationDestination(for: Vacation spot.self) { vacation spot in
                    change vacation spot {
                    case .login:
                        Textual content("Login now")
                    case .most important:
                        Textual content("Essential app")
                    }
                }
        }
        .onAppear {
            path.append(isLoggedIn ? .most important : .login)
        }
    }
}

The issue with this strategy is that until I disable the consumer’s navigation capabilities utilizing navigationBarBackButtonHidden, they will navigate again to the basis view of the NavigationStack. That is problematic as a result of the basis view is merely a placeholder till onAppear pushes the right vacation spot onto the stack.

Utilizing the fullScreenCover view modifier

If I exploit this strategy, I want to connect the fullScreenCover modifier to the primary view. Nevertheless, this poses an issue as a result of I execute some logic when the primary view seems, assuming the consumer is already logged in.

Thanks prematurely in your time!