[KMM] Those who are sharing ViewModels and using S...

# multiplatform

[nrobi]

[KMM] Those who are sharing ViewModels and using SwiftUI on iOS, how do you approach disposing background jobs?
I’m exposing a dispose() and calling it from my ObservableObject ’s deinit method (which represents my view’s state and essentially wraps my ViewModel while publishing the state to the view). Any thoughts if there is a better way?

[zsperske]

I've been thinking about this too. Curious why you prefer deinit to using onDisappear?

[nrobi]

@zsperske that way I don't have to expose neither the vm nor an additional function to the view

[Thomas]

I am using deinit for cancelling the view model coroutine scope. Using onDisappear is not possible, because when that is called the view can still reappear, just like Android onPause/onStop. The deinit is not ideal though, as it does not work well with SwiftUI sheets.

[zsperske]

what happens with sheets?

[Thomas]

When dismissing a sheet the deinit does not get called for ObservableObjects used in that sheet. At least that is what is happening in my project.

[Arkadii Ivanov]

AFAIK SwiftUI may retain gone views just in case they are reused later. I observed this behaviour a while ago.