IssueTracker

We've completed the merge of Navigation Compose specific concepts like routes into the core classes of Navigation (i.e., NavDestination, NavController, etc.). As such, many of the APIs that used to be extension methods are now methods on the classes themselves. This means that a number of imports previously needed can be removed:

import androidx.navigation.compose.navigation
import androidx.navigation.compose.createGraph
import androidx.navigation.compose.getBackStackEntry
import androidx.navigation.compose.navigate
import androidx.navigation.compose.popUpTo

And the KEY_ROUTE can now be accessed simply by calling destination.route.

With these changes, Navigation Compose will join the same versioning scheme as the rest of Navigation and be moved to version 2.4.0-alpha01 for the next version.

Over to Jeremy for plans regarding releasing future versions of navigation.

Another way to reproduce the issue between 2.7.0 (works) and 2.7.1 (broken) is a simple slideIntoContainer and slideOutOfContainer navigation. Hit the button in the example below fast and you'll see animations flying in from the corner instead of sliding!! (btw tested 2.7.5 and its still broken)

class MainActivity : ComponentActivity() {

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContent {
            MaterialTheme {
                val navController = rememberNavController()
                NavHost(navController = navController, startDestination = "first_screen") {

                    composable(
                        route = "first_screen",
                        enterTransition = {
                            slideIntoContainer(
                                towards = AnimatedContentTransitionScope.SlideDirection.Left,
                            )
                        },
                        exitTransition = {
                            slideOutOfContainer(
                                towards = AnimatedContentTransitionScope.SlideDirection.Left,
                            )
                        },
                    ) {
                        FirstScreen {
                            navController.navigate("first_screen")
                        }
                    }

                }
            }
        }
    }
}

@Composable
fun FirstScreen(navigate: () -> Unit) {
    Column(
        modifier = Modifier.fillMaxSize(),
        verticalArrangement = Arrangement.Center,
        horizontalAlignment = Alignment.CenterHorizontally
    ) {

        Button(onClick = {
            navigate()
        }) {
            Text(text = "Navigate!")
        }
    }
}

In 2.7.1 we provided a fix for this issue to ensure Navigation works correctly with Scaffold. Unfortunately, there was a layout bug that was fixed in androidx.compose.ui:ui:1.6.0-alpha03, but since it added new APIs it cannot be backported into a point release of Compose 1.5.x.

Once compose 1.6.0 is stable, we can bump the dependency and release a new version of Navigation with the fix, but until then you can resolve it by either bumping your own compose dependency to use 1.6.x or continuing to use Navigation 2.7.0 if you don't need any of the fixes from the other Navigation point releases.

Navigation 2.8.0-alpha01 has upgraded the Compose dependency to 1.7.0-alpha01 so this will be addressed in the next release.

Since compose 1.6.0 is live can we have a fix for that?

We have the same issue (Compose 1.6.2 and Navigation-Compose 2.7.6).

After explicitly setting the enter and exit transitions, I noticed that on some screens it was working correctly, on others it wasn't. The nav destination screens working correctly were calling the .fillMaxSize() modifier on the outermost/topmost Composable in the view composition hierarchy.

So the accidental/unwanted scale animation seems to have something to do with the sizing of the view children during layouting.

Instead of now having to add sizing modifiers to all destination Composables/screens, adding the .fillMaxSize() modifier to the NavHost itself does the trick. As a result, the specified enter and exit transitions are never overriden by whatever causes the bug.

    NavHost(
        modifier = Modifier.fillMaxSize(),
        navController = navController,
        startDestination = navController.currentBackStackEntry?.destination?.route ?: ProfileDestination.Overview.route(),
        enterTransition = { fadeIn(animationSpec = tween(200)) },
        exitTransition = { fadeOut(animationSpec = tween(200)) }
    )

We observe the same behaviour as described in the previous comment – if size of the NavHost was not zero and changing as a result of navigation, we can see weird left slide-in animation. So I doubt this issue is fixed

Please make sure you've updated to the recently released Navigation 2.8.0-alpha04 and file a new issue if you are still seeing any issues - commenting here will not get your issue fixed.