When using Compose navigation, calls to navigate should be guarded by lifecycle state to prevent invoking navigation methods while composable is transitioning as an effect of navigation. Given navigation destination:

composable(...) { backStackEntry ->
  Screen1(
    ...,
    navigateToScreen2 = { navController.navigate("screen2") },
    ...,
    navigateBack = { navController.popBackStack() },
  )
}

navigation calls should be guarded by backStackEntry lifecycle state to prevent invoking navigation from composable that's under transition:

composable(...) { backStackEntry ->
  Screen1(
    ...,
    navigateToScreen2 = {
      if (backStackEntry.lifecycle.currentState == Lifecycle.State.RESUMED) {
        navController.navigate("screen2")
      }
  },

It would be really useful to have a set of lifecycle aware function wrappers for guarding execution of calls, for example:

fun NavBackStackEntry.whenResumed(onClick: () -> Unit): () -> Unit

or standalone composable version which will use LocalLifecycleOwner to access lifecycle state:

@Composable
fun whenResumed(onClick: () -> Unit): () -> Unit