Fix Fragments not loading ViewModel after App killed in background #4550
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
✨ What kind of change does this PR introduce? (Bug fix, feature, docs update...)
Bug fix
This is due to MvxBindingFragmentAdapter always relying on the Android bundle having saved state, but Android could kill the App in background without going through OnDestroy and related calls.
🆕 What is the new behavior (if this is a feature change)?
Instead of checking for bundle, I am relying on whether ViewModel is null, at this point it will mean, that we didn't navigate to the Fragment using the Presenter and we should load a ViewModel for the Fragment without going to the Presenter.
💥 Does this PR introduce a breaking change?
No
🐛 Recommendations for testing
See steps above
📝 Links to relevant issues/docs
🤔 Checklist before submitting