fix: make sure we only call onDetachedFromWindow once #985
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.
Description
Suggested by @kmagiera change to
ScreenContainer.java
, altering #477, switchingremoveAllViews();
toremoveViewAt(i);
in order to fix the case of callingonDetachedFromWindow
multiple times in the childScreen
s, which can be seen inTest913.tsx
. This behaviors occurs due to the logic ofremoveAllViews
method, which does not check if the child views are not already detached when the method is called, whereas the check is present inremoveViewAt
method (see https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/view/ViewGroup.java#5559 which is not present in https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/view/ViewGroup.java#5771).Test code and steps to reproduce
Test913.tsx
inTestsExample
project.Checklist