Problem

In the DebloaterScreen, component toggle switches would not update in the UI after enabling/disabling a component, even though the controller successfully changed the component state. Users had to restart the app to see the changes.

Root Cause

The DebloaterViewModel used a continuous flow collection pattern that would overwrite optimistic UI updates when new data was emitted from the repository. The init block had:

init {
    viewModelScope.launch {
        debloatableComponentsFromRepository.collect { result ->
            _debloatableUiState.value = result  // Overwrites optimistic updates!
        }
    }
}

Solution

Refactored DebloaterViewModel to use one-time data loading with .first() similar to the RuleDetailViewModel pattern:

• Changed from continuous flow collection to one-time loading in loadData() method
• Added drop(1) to search query collection to avoid duplicate loads on initialization
• Updated tests to initialize data before ViewModel creation

This prevents repository emissions from overwriting the optimistic UI updates made during component control operations.

Testing

• All existing unit tests updated and passing
• Verified component toggle behavior matches RuleDetailViewModel (SDK page) pattern