[Question] What is the best way to deep link to the second/third screen in the app? about stinsen

[rundfunk47]

Hi! I've checked this and it indeed seems like a bug. I'll investigate further...!

[sbilling]

@rundfunk47 I am still very curious about this one. I am actually trying to implement UNAuthorizationOptionProvidesAppNotificationSettings which provides a deeplink to in-app notification settings within my app. I get to this screen by focusing my profile tab, and then routing to settings (which pushes a new coordinator) and then calling a route(to: .notifications) on that coordinator. The chain looks like this (it begins with a notification center listener applied in my MainCoordinator (parent all of other coordinators)

.onReceive(NotificationCenter.default.publisher(for: .settingsRouteAction), perform: { _ in
               self.focusFirst(\.profile)
                    .child
                    .popToRoot()
                    .route(to: \.settings)
                    .route(to: \.notifications)
            })

The chain works as expected until the very end. It focuses the profile tab, pushes to settings, and then pushes to notifications. BUT the start function gets called again after the push of notifications and it actually pops back to the settings view (before notifications). Any idea why?

I should note that this actually works if the notifications view is nested in its own NavigationViewCoordinator BUT that leads to a duplicative nav bar because its being pushed by the settings coordinator.

[rundfunk47]

Hi! I might be unsure what you mean, but the code you showed should work, provided that you have something like::

@Route(.push) var todoDetail = makeTodoDetail

in TodosCoordinator.swift

[schrulnz]

Thanks for the fast reply. So a chain of two (push) routes should generally work?

I have been trying to do this in the stinsen/Examples/App code, by adding a todoDetail in HomeScreen like this (the detail screen is just displaying some text for now):

                     Button(todo.name) {
                            authenticatedRouter
                                .focusFirst(\.todos)
                                .child
                                .popToRoot()
                                .route(to: \.todo, todo.id)
                                .route(to: \.detail, todo.id)
                     }

However, this only navigates the app to the Todos tab (and neither the todo screen nor the detail screen) and I don't get any errors in the console. If I only navigate to .todo OR .detail, the navigation works fine for each of the views, but never if I do both navigations.

[MartinaRogach]

i'm interested in this question also

[abrown252]

I'd love to know if this is possible!

[PeterKovacs89]

@rundfunk47 Any update about this topic? We would like to use your library to support deep linking in our app, and chaining route(to:) calls would be crucial for us. Looking forward to hearing from you and thank you for your great work!

[nunocaseiro]

The chain navigation isn't possible. Is it a bug that can be fixed? Can we get an update on this?