LiveData未触发更新排查：账号创建页按钮状态无响应问题

核心问题 #

1. 状态容器适配错误：你在ViewModel中使用了Compose专属的mutableStateOf存储邮箱和手机号，但该状态的变化通知依赖Compose的Snapshot上下文，ViewModel中直接赋值的操作无法被snapshotFlow正确捕捉，导致后续验证逻辑完全不触发。
2. 逻辑运算符优先级错误：it.first ?: false && it.second ?: false中&&优先级高于?:，实际执行逻辑会变成it.first ?: (false && it.second ?: false)，导致按钮状态计算结果完全不符合预期。

修复后的代码（推荐简洁版） #

直接使用StateFlow+combine简化逻辑，避免自定义MediatorLiveData的冗余：

@HiltViewModel
class CreateAccountEnterEmailViewModel @Inject constructor(
    appData: AppData,
) : ViewModel() {
    // 改用ViewModel适配的StateFlow存储状态
    private val _email = MutableStateFlow("")
    private val _phoneNumber = MutableStateFlow("")

    private var _isPhoneNumberFieldVisibleState: MutableStateFlow<Boolean> = MutableStateFlow(appData.isPhoneNumberRequiredForRegistrationParam.orDef())
    val isPhoneNumberFieldVisible: LiveData<Boolean> = _isPhoneNumberFieldVisibleState.asLiveData()

    // 直接合并两个状态的验证结果
    val isContinueBtnEnabled: LiveData<Boolean> = combine(_email, _phoneNumber) { email, phone ->
        validateEmail(email) && validatePhone(phone)
    }.asLiveData()

    fun updateEmail(email: String) {
        _email.value = email
    }

    fun updatePhoneNumber(phoneNumber: String) {
        _phoneNumber.value = phoneNumber
    }

    // 保留你的验证逻辑实现
    private fun validateEmail(email: String): Boolean {
        // 你的邮箱验证逻辑
    }

    private fun validatePhone(phone: String): Boolean {
        // 你的手机号验证逻辑
    }
}

修复后的代码（兼容原逻辑结构版） #

如果需要保留原有的LiveData组合方式，需修复状态容器和运算符优先级：

@HiltViewModel
class CreateAccountEnterEmailViewModel @Inject constructor(
    appData: AppData,
) : ViewModel() {
    // 替换为StateFlow
    private val _email = MutableStateFlow("")
    private val _phoneNumber = MutableStateFlow("")

    private var _isPhoneNumberFieldVisibleState: MutableStateFlow<Boolean> = MutableStateFlow(appData.isPhoneNumberRequiredForRegistrationParam.orDef())
    val isPhoneNumberFieldVisible: LiveData<Boolean> = _isPhoneNumberFieldVisibleState.asLiveData()

    class PairMediatorLiveData<F, S>(firstLiveData: LiveData<F>, secondLiveData: LiveData<S>) : MediatorLiveData<Pair<F?, S?>>() {
        init {
            addSource(firstLiveData) { first ->
                value = first to secondLiveData.value
            }
            addSource(secondLiveData) { second ->
                value = firstLiveData.value to second
            }
        }
    }

    private val isEmailValid: LiveData<Boolean> = _email
        .map { validateEmail(it) }
        .asLiveData()

    private val isPhoneValid: LiveData<Boolean> = _phoneNumber
        .map { validatePhone(it) }
        .asLiveData()

    val isContinueBtnEnabled: LiveData<Boolean> = PairMediatorLiveData(isEmailValid, isPhoneValid)
        .switchMap { pair ->
            liveData {
                // 修复运算符优先级问题
                emit((pair.first ?: false) && (pair.second ?: false))
            }
        }

    fun updateEmail(email: String) {
        _email.value = email
    }

    fun updatePhoneNumber(phoneNumber: String) {
        _phoneNumber.value = phoneNumber
    }

    private fun validateEmail(email: String): Boolean {
        // 你的邮箱验证逻辑
    }

    private fun validatePhone(phone: String): Boolean {
        // 你的手机号验证逻辑
    }
}

关键修复点说明 #

1. 替换状态容器：MutableStateFlow是专为ViewModel等非Compose场景设计的状态容器，状态变化可被Flow正确监听，确保输入更新后验证逻辑及时触发。
2. 修正运算优先级：给每个空值默认值表达式添加括号，保证逻辑与的运算顺序符合预期。
3. 可选优化：使用combine操作符直接合并两个StateFlow，省去自定义MediatorLiveData的复杂逻辑，代码更简洁可靠。

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