MvvmCross-AndroidSupport
MvvmCross-AndroidSupport copied to clipboard
In MvxCachingFragmentActivity, receiving a ViewModelRequest with different parameters of a frag already being shown, should trigger the ViewModel Lifecycle
Currently, if we need to show a viewmodel with different parameters with a visible fragment, the process will be blocked somewhere inside MvvmCross. This needs to be changed in order to support the ViewModel lifecycle reload, so it receives the new parameters and by databinding, the current view should adapt to it.
Can you check again with the code after PR: https://github.com/MvvmCross/MvvmCross-AndroidSupport/pull/149 ?