How to create and initialize a CoreData object before navigating to a new view in SwiftUI?

Question

I have a SwiftUI app with two views:

• SessionListView

struct SessionListView: View {

    @FetchRequest(
        entity: Session.entity(),
        sortDescriptors: [NSSortDescriptor(keyPath: \Session.timestamp, ascending: false)],
        predicate: NSPredicate(format: "finishedTimestamp == nil"),
        animation: .default)
    private var openSessions: FetchedResults<Session>

    [...]

    var body: some View {
        if let openSession = openSessions.first {
            NavigationLink(destination: NewSessionView(session: openSession)) {
                Text("Continue Current Session")
            }
        } else {
            NavigationLink(destination: NewSessionView(session: *?*) {
                Text("Create New Session")
            }
        }

    }
}

• NewSessionView (more like ActiveSessionView)

struct NewSessionView: View {

    @ObservedObject var session: Session;

    var body: Some View {
        [...]
    }

}

My desired outcome is that if the FetchRequest returns an item, we pass the existing item from SessionListView to NewSessionView. If the FetchRequest returns no results, we create a new item, and initialize the timestamp variable as such:

private func createNewSession() {
    let newSession = Session(context: viewContext)
    newSession.timestamp = Date()

    do {
        try viewContext.save()
        isNewSessionCreated = true
    } catch {
        let nsError = error as NSError
        fatalError("Unresolved error when creating a new session \(nsError), \(nsError.userInfo)")
    }
}

I've tried adding:

NavigationLink(destination: NewSessionView(session: newSession)) {
    EmptyView()
}

at the of createNewSession and calling the method on button click rather than using a NavigationLink in the View itself but that resulted in the session being created and the button text changing to "Continue Current Session". So it did technically work, but it required the user to perform one extra action of clicking the "Continue Current Session" which is terrible design.

I've tried using the isActive binding as described here, but that appears to be deprecated and brought challenges of its own.

I would like to keep the actual creation and initialization of the Session object in the SessionListView and not the NewSessionView if possible.

Does anyone have any pointers I can follow to achieve this? I can post more examples of what I've tried if it helps as well. Thanks!