Android ViewModel协程异常处理问题：错误信息无法显示到UI

问题根源 #

• 同步校验（如字符长度超限）在addCategory函数执行时直接抛出异常，Fragment的try-catch能捕获；
• 协程内的异步代码（如分类数量超限校验）抛出异常时，addCategory函数已经执行完毕，Fragment的try-catch无法覆盖这部分异步逻辑的异常；
• 在CoroutineExceptionHandler中重新抛出异常会导致崩溃，因为viewModelScope的上下文没有上层协程处理该异常。

解决方案：用StateFlow/LiveData传递错误状态 #

推荐使用StateFlow（Jetpack偏好的响应式状态方案）来统一传递同步和异步异常信息，确保UI能实时接收并显示错误。

1. 修改ViewModel代码

class CategoryViewModel(private val categoryRepository: CategoriesRepository) : ViewModel() {
    // 定义用于传递错误信息的StateFlow
    private val _errorMessage = MutableStateFlow<String?>(null)
    val errorMessage: StateFlow<String?> = _errorMessage

    fun addCategory(categoryName: String, categoryIconId: Int?, type: String) {
        // 同步校验：将错误信息发送到StateFlow，而非直接抛出
        if (categoryName.length > 20) {
            _errorMessage.value = "Maximum character limit reached"
            return
        }

        viewModelScope.launch {
            try {
                val categoryCount = categoryRepository.getCategoryCount(null).first()
                if (categoryCount >= 10) {
                    _errorMessage.value = "Maximum category limit reached"
                    return@launch
                }

                val categoryObject = Category(name = categoryName, iconId = categoryIconId, type = type)
                categoryRepository.insertCategory(categoryObject)
                // 成功后清空错误信息
                _errorMessage.value = null
            } catch (e: Exception) {
                // 捕获仓库操作可能抛出的其他异常
                _errorMessage.value = e.message
            }
        }
    }
}

2. 修改Fragment代码

在Fragment的生命周期内收集StateFlow的错误信息，更新UI：

override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
    super.onViewCreated(view, savedInstanceState)
    
    // 收集错误信息并更新TextInputLayout
    lifecycleScope.launch {
        repeatOnLifecycle(Lifecycle.State.STARTED) {
            categoryVM.errorMessage.collect { errorMsg ->
                textInputLayout.error = errorMsg
            }
        }
    }

    // 调用addCategory时无需try-catch，统一由StateFlow处理
    yourAddButton.setOnClickListener {
        val categoryName = ... // 获取输入的分类名
        val iconId = ... // 获取图标ID
        val type = ... // 获取类型
        categoryVM.addCategory(categoryName, iconId, type)
    }
}

替代方案：使用LiveData #

如果更习惯用LiveData，可替换StateFlow为LiveData：

ViewModel代码

class CategoryViewModel(private val categoryRepository: CategoriesRepository) : ViewModel() {
    private val _errorMessage = MutableLiveData<String?>()
    val errorMessage: LiveData<String?> = _errorMessage

    fun addCategory(categoryName: String, categoryIconId: Int?, type: String) {
        if (categoryName.length > 20) {
            _errorMessage.value = "Maximum character limit reached"
            return
        }

        viewModelScope.launch {
            try {
                val categoryCount = categoryRepository.getCategoryCount(null).first()
                if (categoryCount >= 10) {
                    _errorMessage.value = "Maximum category limit reached"
                    return@launch
                }

                val categoryObject = Category(name = categoryName, iconId = categoryIconId, type = type)
                categoryRepository.insertCategory(categoryObject)
                _errorMessage.value = null
            } catch (e: Exception) {
                _errorMessage.value = e.message
            }
        }
    }
}

Fragment代码

override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
    super.onViewCreated(view, savedInstanceState)
    
    categoryVM.errorMessage.observe(viewLifecycleOwner) { errorMsg ->
        textInputLayout.error = errorMsg
    }

    yourAddButton.setOnClickListener {
        val categoryName = ...
        val iconId = ...
        val type = ...
        categoryVM.addCategory(categoryName, iconId, type)
    }
}

关键说明 #

• 统一用状态流传递错误，避免同步/异步异常处理不一致的问题；
• 使用repeatOnLifecycle（StateFlow）或viewLifecycleOwner（LiveData）确保UI仅在活跃状态下接收更新，避免内存泄漏；
• 操作成功后清空错误信息，防止屏幕旋转等配置变更后错误依然显示。

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