State Update Issue in Composable Navigation

[mlouli]

Hello, I've got a question about the implementation of composable navigation.

I implemented a complete flow as mentioned in this composable navigation post. I grouped all the possible sheets my app can present into a single view, which we'll call the 'master sheet'. This sheet has an enum of all possible child sheets as a state property.

All these child sheets utilize TCA.

My issue is, even after implementing the technique from the article, when a child sheet updates its state, the view doesn't register this change. But when the same child sheet is presented directly from the parent, everything operates smoothly.

Could this be a limitation, bug, or am I possibly making a mistake?

Thank you in advance.

[mbrandonw]

Hi @mlouli, first I would suggest following the tutorials in the repo rather than that blog post, which was posted many months ago at the beginning of the beta period.

And second, it's hard to say what the problem is without seeing some code. Can you share a minimal project that demonstrates the problem you are seeing?

[mlouli]

I have a similar setup with swift-composable-architecture 0.54.1. Upgrading to v0.56.0 didn't resolve the issue. I'm also using swiftui-navigation 0.8.0.

Simulator.Screen.Recording.-.iPhone.14.Pro.-.2023-07-19.at.21.06.41.mp4

[mbrandonw]

Can you upload a project that demonstrates the problem? I just copied and pasted your code into an existing project.

[mlouli]

Sorry for the delay; I needed to sanitize the project data. Surprisingly, the identical code runs perfectly in a fresh project.

The shared project should illustrate the problem.

Debug.zip

[mbrandonw]

I didn't notice in your first code snippet, but the problem is that you are creating a whole new store from scratch to pass along to the child view:

      case .child:
        ModalWrapper {
          ChildView(store: .init(
            initialState: .init(),
            reducer: Child()
          ))
        }

That store is fully disconnected from the parent store, and so it is not surprising that it isn't picking up state changes. Typically one derives a store from the parent to hand down to the child.

It seems that either that state should not be an enum, or you should follow the steps outlined in the tutorial (in particular this section) to see how to properly drive navigation from an enum of destinations.

[mlouli]

Thanks for your quick responses; the tutorial section you pointed out is indeed quite clear.

Enjoy the rest of your day!