Giannis Tsepas

is there any more elegant way to fix this memory leak?

I can confirm the same issue.

The deprecated LifecycleActivity and LifecycleFragment have now been removed - please use FragmentActivity, AppCompatActivity or support Fragment.

I would like to see this, too. But in case you want to implement your own async command take a look here: https://msdn.microsoft.com/en-us/magazine/dn630647.aspx https://github.com/StephenCleary/Mvvm.Async

are you looking for something like this? http://dotnetpattern.com/mvvm-light-messenger There is a way for custom messenger.

just out of curiosity, why would you need that? Any practical example?

can you please state if you noticed this issue on an actual device or emulator? I tested on an emulator with Android 12 and it works.