如何在Jetpack Compose中从其他界面访问状态？

针对你代码里Screen2无法访问Screen1中index状态的问题，以下是几种可行的实现方式：

方案一：将状态提升到NavGraph层级 #

把共享状态提到NavComposable的父级（NavGraph），通过参数传递给子Composable，子界面借助回调修改状态：

@Composable
fun NavGraph(navController: NavHostController) {
    // 将共享状态提升到NavGraph层级
    var index by remember { mutableIntStateOf(0) }
    
    NavHost(
        navController = navController,
        startDestination = "screen1"
    ) {
        composable(route = "screen1") {
            Screen1(navController = navController, index = index)
        }
        composable(route = "screen2") {
            Screen2(navController = navController, onIndexIncrement = { index++ })
        }
    }
}

@Composable
fun Screen1(navController: NavHostController, index: Int) {
    Button(onClick = {
        navController.navigate(route = "screen2")
    }) {
        Text(text = "Screen1 $index")
    }
}

@Composable
fun Screen2(navController: NavHostController, onIndexIncrement: () -> Unit) {
    Button(onClick = onIndexIncrement) {
        Text(text = "Screen2")
    }
}

这种方式适合简单状态共享，状态由父级统一持有，子界面只负责触发修改动作。

方案二：使用共享ViewModel #

利用Jetpack ViewModel的生命周期特性，在NavHost范围内创建ViewModel，确保所有子Composable共享同一个实例：

先添加ViewModel依赖（若未引入）：

implementation "androidx.lifecycle:lifecycle-viewmodel-compose:2.6.2"

实现共享ViewModel和界面：

// 定义共享ViewModel
class SharedViewModel : ViewModel() {
    val index = mutableIntStateOf(0)
    
    fun incrementIndex() {
        index.value++
    }
}

@Composable
fun NavGraph(navController: NavHostController) {
    // 在NavHost范围内创建ViewModel，保证所有子界面共用同一实例
    val viewModel = viewModel<SharedViewModel>()
    
    NavHost(
        navController = navController,
        startDestination = "screen1"
    ) {
        composable(route = "screen1") {
            Screen1(navController = navController, viewModel = viewModel)
        }
        composable(route = "screen2") {
            Screen2(navController = navController, viewModel = viewModel)
        }
    }
}

@Composable
fun Screen1(navController: NavHostController, viewModel: SharedViewModel) {
    Button(onClick = {
        navController.navigate(route = "screen2")
    }) {
        Text(text = "Screen1 ${viewModel.index.value}")
    }
}

@Composable
fun Screen2(navController: NavHostController, viewModel: SharedViewModel) {
    Button(onClick = { viewModel.incrementIndex() }) {
        Text(text = "Screen2")
    }
}

这种方式适合复杂状态或多界面共享场景，ViewModel会在NavHost生命周期内保持，不会随界面销毁丢失状态。

方案三：用SavedStateHandle持久化状态（可选） #

如果需要进程重启后保留状态，可在ViewModel中结合SavedStateHandle实现：

class SharedViewModel(savedStateHandle: SavedStateHandle) : ViewModel() {
    private val _index = savedStateHandle.getStateFlow("index", 0)
    val index = _index.asStateFlow()
    
    fun incrementIndex() {
        savedStateHandle["index"] = _index.value + 1
    }
}

// 界面中收集Flow更新状态
@Composable
fun Screen1(navController: NavHostController, viewModel: SharedViewModel) {
    val index by viewModel.index.collectAsState()
    Button(onClick = {
        navController.navigate(route = "screen2")
    }) {
        Text(text = "Screen1 $index")
    }
}

内容的提问来源于stack exchange，提问作者Jorpy