second way to fix activity leak after configuration change #418
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.
In continuation to this PR
#415
I think this solution is better and i also checked it in our project
I don't actually see where
onDispose
inAndroidScreenLifecycleOwner
would be called when configuration changes. And I think it's the client ofAndroidScreenLifecycleOwner
responsibility to decide when to dispose it@DevSrSouza what to you think?