Nested Presenters and Navigation Issue

[LloydBlv]

I have read the docs about nested navigation and looked at samples folder, but could not find an answer to the following issue I am facing:

Let's say I have the following code on the top level of my layout:

val backstack = rememberSaveableBackStack(root = InitialScreen)
                val navigator =
                    rememberAndroidScreenAwareNavigator(
                        delegate = rememberCircuitNavigator(backstack),
                        starter = remember { AndroidScreenStarter(::handleLegacyScreen) },
                    )

                CompositionLocalProvider(LocalErrorFormatter provides errorFormatter) {
                    CircuitCompositionLocals(
                        circuit = circuit,
                        content = { NavigableCircuitContent(navigator, backstack) },
                    )
                }

If I have a presenter at the InitialScreen level, and I have a CircuitContent as ChildPresenter in a view that is inside the InitialScreen, How can I navigate InitialScreen to another screen while the code in the ChildPresenter is used for navigation?

I tried adding a navEvent argument to the inner CircuitContent but this causes the ChildPresenter to be called multiple times (makes it unstable?) and messes up some API calls.

This is how the child content is structured:

@Composable
private fun ChildScreenView(
    id: String,
    onSomethingClicked: (NavEvent) -> Unit
) {
    CircuitContent(
        key = uid,
        screen = ChildScreen(id),
        onNavEvent = onSomethingClicked
    )
}

Compose compiler report shows that this is stable:

restartable skippable fun ChildScreenView(
  stable id: String
  stable onSomethingClicked: Function1<NavEvent, Unit>
)

but having Timber.i("child.present(%s), screen=%s", this, screen) inside the present() function of the ChildPresenter shows that it gets called with different object hashes, If I remove the onNavEvent everything works fine but my event is not picked up