Did anyone get issue with viewModelScope ? `viewModelScope.launch` work like a charm until I’m navig...

# android

[Breaker ACT]

Did anyone get issue with viewModelScope ?
viewModelScope.launch work like a charm until I’m navigate to other screen => viewModel go to onClear() => Then I’m navigate back and try to call viewModelScope.launch but it didn’t anything. Any idea for this ?

[Casey Brooks]

The viewModelScope gets cancelled once the ViewModel itself is cleared, and you can’t launch new jobs in a cancelled coroutineScope. You might have an issue with how you’re accessing your ViewModel. How are you creating your ViewModel?

[Breaker ACT]

@Casey Brooks I’m using this syntax to create a ViewModel

protected open val viewModel: VM by lazy { ViewModelProvider(this)[ViewModelClass::kt] }

[Breaker ACT]

So I pass this as the viewModelStoreOwner. Any incorrect at here

[Casey Brooks]

Yeah, I’m thinking by lazy isn’t what you want, that it will hold onto a ViewModel instance longer than it should. You should probably be using the by viewModels() function from the fragment-ktx library

[Breaker ACT]

@Casey Brooks Thanks. Let me try

[Breaker ACT]

@Casey Brooks by viewModels() didn’t resolve my issue. Any other idea

[Tower Guidev2]

are you accessing a viewmodel from a fragment? and then navigating to other fragments?
as you will need to obtian your view model within the fragment using

val viewModel: MyViewModel by activityViewModels<YourViewModel>()

and NOT

val viewModel by viewModels<YourViewModel>()