IssueTracker

I just encountered the same issue. This causes unexpected behavior as navigation does not occur when navigate is called, but does suddenly occur if recomposition is triggered externally.

I attached a video demonstrating the behavior, it runs the following code:

package com.example.delayednavigation

import android.os.Bundle
import androidx.activity.ComponentActivity
import androidx.activity.compose.setContent
import androidx.compose.foundation.layout.*
import androidx.compose.material.Button
import androidx.compose.material.Text
import androidx.compose.runtime.*
import androidx.compose.ui.Modifier
import androidx.compose.ui.unit.dp
import androidx.navigation.NavController
import androidx.navigation.compose.*

class MainActivity : ComponentActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContent {
            val navController = rememberNavController()
            var counter by remember { mutableStateOf(0) }

            Column(
                Modifier.fillMaxSize().padding(24.dp)
            ) {
                NavHost(
                    navController = navController,
                    startDestination = "home"
                ) {
                    composable("home") {
                        Text(text = "Route: /home")
                        Spacer(Modifier.height(24.dp))

                        NavigationButtons(navController = navController)
                    }
                    composable("page/{id}") {
                        Column(verticalArrangement = Arrangement.Center) {
                            Text(text = "Route: page/${it.arguments!!["id"]}")
                            Spacer(Modifier.height(24.dp))

                            Text(text = "Counter: $counter")
                            Spacer(Modifier.height(24.dp))

                            NavigationButtons(navController = navController)
                            Button(onClick = { counter += 1 }) {
                                Text("Recompose")
                            }
                        }
                    }
                }

            }
        }
    }
}

@Composable
fun NavigationButtons(
    navController: NavController
) {
    Column {
        (1..3).forEach { pageId ->
            Button(
                modifier = Modifier.padding(bottom = 24.dp),
                onClick = {
                navController.navigate("page/$pageId") {
                    launchSingleTop = true
                }
            }) {
                Text("Navigate to page $pageId")
            }
        }
    }
}

This was with navigation-compose:2.4.0-alpha03 and compose:1.0.0-beta09.

This has been fixed internally and will be available in the Navigation 2.4.0-alpha07 release.

You can try this out by following the snapshot instructions and using Build Id #7634339.

I tried the new snapshot version, but it doesn't seem to be working for me.

Using a debugger, I verified that the new NavigatorState.onLaunchSingleTop() was called, and the updatedBackStack that was set with the expected argument update.

However, the NavHost's composable still doesn't get recomposed. Is it possible that arguments are somehow being filtered out in state update changes?

Please file a new bug with a minimal sample project that reproduces your issue.

The sample code in the original report (#comment1) still demonstrates the issue.

The issue in #comment2 is also still happening. For example, in the code from #comment1, notice how tapping the button does not update the value as expected: it always stays Empty. But if you leave the app open and toggle the system dark mode, now the app will get recomposed with the new value2.

If it helps, I can share the project, but it's really just the code from #comment1 put in an "Empty Compose Activity" project.

Yeah, sorry looks like we still haven't fixed this. Somehow our test, which is very similar to the code in #1 passes, but in practice we still aren't recomposing.

We were able to get a fix for this in Navigation 2.4.0-alpha08.

You can try this out by following the snapshot instructions and using Build Id #7677699.

Please file a new bug with a minimal sample project that reproduces the issue.

The same issue still exists.

Re comment#17 - you'll want to file a new bug with a sample project that reproduces the issue you're still experiencing.