Impossible to set a state that push a view then a modal or another push 🤔

[FredericRuaudel]

Hello everyone!

For debugging purpose, marketing screenshots or deeplinking features, I would like to set my route state deep in my view hierarchy in one shot but some cases doesn't work:

• modal then modal -> ✅
• push then modal -> ❌
• push then push -> ❌

I'm afraid, this is a "bug" in SwiftUI that have limitation by using UIKit under the hood since double modal is ok.

I would like to be able to set the state in a reducer for deeplinking like this:

case .pushedAndShowModalButtonTapped:
  state.route = .details(Pushed1State(route: .modal(Modal1State())))
  return .none

Or directly as an initial state for debugging or screenshoting like this:

AppView(store: .init(
  initialState: .init(route: .details(Pushed1State(route: .modal(Modal1State())))),
  reducer: appReducer.debug(),
  environment: ())
)

In some cases, I get errors like this but not always:

2022-05-19 10:13:50.528088+0200 TCAMultiModalState[75063:918825] [Presentation] Attempt to present
<_TtGC7SwiftUI29PresentationHostingControllerVS_7AnyView_: 0x13f92bb00> on 
<_TtGC7SwiftUI19UIHostingControllerGVS_15ModifiedContentVS_7AnyViewVS_24NavigationColumnModifier__: 0x13f91a090> (from <_TtGC7SwiftUI19UIHostingControllerGVS_15ModifiedContentVS_7AnyViewVS_24NavigationColumnModifier__: 
0x13f91a090>) whose view is not in the window hierarchy.

So I tried to disable animations like this, but with no success:

Button("Pushed View 1 and Show Modal 1") {
  viewStore.send(.pushedAndShowModalButtonTapped, animation: .none)
}

If anyone have a suggestion, I'll be very thankful ! 🙏

Here is a sample code that demonstrate this with minimum code:

TCAMultiModalState.zip

[FredericRuaudel]

I've maybe found my answer in johnpatrickmorgan repo:
https://github.com/johnpatrickmorgan/TCACoordinators/#making-complex-navigation-updates

That he mentions in the #1006 discussion about deeplinking. I'll try to refactor my sample code with TCACoordinators to see if it fixes my issues...

[FredericRuaudel]

Ok, I confirm that TCACoordinator is fixing my issue partly :

1. very elegantly for the deeplinking part where I need to navigate deeply in my hierarchy using one action.
2. But for the test/screenshot part where we need to set the initialState directly, the solution I've found is working but half satisfying.

I've added an var initialAction: CoordinatorAction? to my CoordinatorState so that I can set a special action that will do all the push/present ScreenActions needed to go where I need using the routeWithDelaysIfUnsupported effect if necessary. Then I run this action in onAppear of my CoordinatorView if not nil. It has the drawbacks to pollute my production code but at least it can be confined only in the Coordinator module. 😐

Here is the final sample code updated:

TCAMultiModalStateWithTCACoordinator.zip

Hope that Apple will fix this "bug" in a future iOS release 🤞