Tree-based navigation deeplinking shows mostly blank screens about swift-composable-architecture HOT 2 CLOSED

Additional comment for the issue

According to the logs that are provided by _printChanges(),
at the first, the states are well-assigned but immediately .destination(.dismiss) is called from the parent reducer via navigationDestination method:

received action:
  AppReducer.Action.secondTapped
- AppReducer.State(_destination: nil)
+ AppReducer.State(
+   _destination: .first(
+     FirstReducer.State(
+       _destination: .second(
+         SecondReducer.State(_destination: nil)
+       )
+     )
+   )
+ )

received action:  // ❌ unexpected action is called
  AppReducer.Action.destination(
    .presented(
      .first(
        .destination(.dismiss)
      )
    )
  )
  AppReducer.State(
    _destination: .first(
-     FirstReducer.State(
-       _destination: .second(
-         SecondReducer.State(_destination: nil)
-       )
-     )
+     FirstReducer.State(_destination: nil)
    )
  )

from swift-composable-architecture.

I believe this is a vanilla SwiftUI bug with navigationDestination, though if you can show it working there we can look into if it's a TCA bug.

We provide a workaround in our SwiftUINavigation package, but have decided against doing so in TCA, since it introduces a flakey code path that could break at any time when Apple fixes things. There's recent discussion here about how the modifier has regressed in iOS 17, and a possible workaround you can bring to your TCA project: pointfreeco/swiftui-navigation#121

I'm going to convert this to a discussion, since it appears to be an Apple bug and not a bug with the library.

from swift-composable-architecture.