Android中StateFlow调用方法后Activity未更新状态问题解决

问题描述 #

在Android应用的MVI架构中，使用StateFlow替代LiveData做状态管理。点击按钮触发MainIntent.FilterNote意图时，ViewModel中已打印Empty from viewmodel日志，但Activity未执行MainState.Empty分支的逻辑。相关代码如下：

ViewModel代码 #

@HiltViewModel
class MainViewModel @Inject constructor(private val repository: MainRepository) : ViewModel() {
    val mainIntent = Channel<MainIntent>()
    private val _state = MutableStateFlow<MainState>(MainState.Empty)
    val state: StateFlow<MainState> get() = _state

    init {
        handleIntent()
    }

    private fun handleIntent() {
        viewModelScope.launch {
            mainIntent.consumeAsFlow().collect {
                when (it) {
                    is MainIntent.LoadAllNotes -> fetchingAllNotesList()
                    is MainIntent.FilterNote -> fetchingFilterNotes(it.filter)
                }
            }
        }
    }

    private fun fetchingAllNotesList() {
        _state.value = MainState.LoadNotes(repository.allNotes())
    }


    private fun fetchingFilterNotes(filter: String) {
        _state.value = MainState.Empty
        Log.e("DataLog", "Empty from viewmodel")
    }
}

Activity代码 #

lifecycleScope.launch {
            //Send
            viewModel.mainIntent.send(MainIntent.LoadAllNotes)
            //Get
            viewModel.state.collect { state ->
                when (state) {
                    is MainState.Empty -> {
                        Log.e("DataLog", "Empty on activity")
                        emptyLay.visibility = View.VISIBLE
                        notesList.visibility = View.GONE
                    }
                    is MainState.LoadNotes -> {
                        Log.e("DataLog", "Load notes")
                        emptyLay.visibility = View.GONE
                        notesList.visibility = View.VISIBLE
                        state.list.collect {
                            noteAdapter.setData(it)
                            notesList.apply {
                                layoutManager = StaggeredGridLayoutManager(2, StaggeredGridLayoutManager.VERTICAL)
                                adapter = noteAdapter
                            }
                        }
                    }
                }
            }
        }

原因分析 #

核心问题是Activity中MainState.LoadNotes分支内的state.list.collect是挂起函数，会阻塞外层的viewModel.state.collect流。当状态切换到LoadNotes后，协程会卡在state.list.collect的循环中，无法回到外层去处理ViewModel新发送的Empty状态。

解决方案 #

方案1：开启新协程处理列表流 #

在LoadNotes分支中，用新的协程去收集列表数据，避免阻塞外层的状态收集：

lifecycleScope.launch {
    viewModel.mainIntent.send(MainIntent.LoadAllNotes)
    viewModel.state.collect { state ->
        when (state) {
            is MainState.Empty -> {
                Log.e("DataLog", "Empty on activity")
                emptyLay.visibility = View.VISIBLE
                notesList.visibility = View.GONE
            }
            is MainState.LoadNotes -> {
                Log.e("DataLog", "Load notes")
                emptyLay.visibility = View.GONE
                notesList.visibility = View.VISIBLE
                // 启动新协程处理列表收集，不阻塞外层状态流
                lifecycleScope.launch {
                    state.list.collect {
                        noteAdapter.setData(it)
                        notesList.apply {
                            layoutManager = StaggeredGridLayoutManager(2, StaggeredGridLayoutManager.VERTICAL)
                            adapter = noteAdapter
                        }
                    }
                }
            }
        }
    }
}

方案2：调整状态设计，避免嵌套收集 #

修改状态结构，将列表更新作为独立状态发送，彻底消除嵌套collect的阻塞问题：

ViewModel修改

private fun fetchingAllNotesList() {
    viewModelScope.launch {
        // 先发送加载状态（可选）
        _state.value = MainState.Loading
        // 收集列表数据，转换成独立状态发送
        repository.allNotes().collect { notes ->
            _state.value = MainState.UpdateNotes(notes)
        }
    }
}

Activity修改

lifecycleScope.launch {
    viewModel.mainIntent.send(MainIntent.LoadAllNotes)
    viewModel.state.collect { state ->
        when (state) {
            is MainState.Empty -> {
                Log.e("DataLog", "Empty on activity")
                emptyLay.visibility = View.VISIBLE
                notesList.visibility = View.GONE
            }
            is MainState.Loading -> {
                // 显示加载UI（可选）
            }
            is MainState.UpdateNotes -> {
                Log.e("DataLog", "Update notes")
                emptyLay.visibility = View.GONE
                notesList.visibility = View.VISIBLE
                noteAdapter.setData(state.list)
                notesList.apply {
                    layoutManager = StaggeredGridLayoutManager(2, StaggeredGridLayoutManager.VERTICAL)
                    adapter = noteAdapter
                }
            }
        }
    }
}

说明 #

两种方案都能解决状态阻塞问题：方案1更贴合现有代码结构，改动量小；方案2更符合MVI的单一状态流设计原则，逻辑更清晰。

内容的提问来源于stack exchange，提问作者Dr.KeyOk