Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Layout Animations][iOS] Fix registering exiting view ancestors #3849

Merged
merged 3 commits into from
Dec 14, 2022

Conversation

jwajgelt
Copy link
Contributor

@jwajgelt jwajgelt commented Dec 9, 2022

Summary

#3824 introduces a bug with how we register ancestors of views with exiting animations.
When a tree with exiting views is reattached to the native view hierarchy, we don't register the ancestors of that tree as ancestors of exiting subviews. This may cause issues with deleting these views early, while there're still exiting animations running inside them.

Test plan

@jwajgelt jwajgelt self-assigned this Dec 9, 2022
@jwajgelt jwajgelt marked this pull request as ready for review December 9, 2022 14:43
@jwajgelt jwajgelt merged commit a10752e into main Dec 14, 2022
@jwajgelt jwajgelt deleted the @jwajgelt/layout_animations_register_ancestors_ios branch December 14, 2022 10:21
fluiddot pushed a commit to wordpress-mobile/react-native-reanimated that referenced this pull request Jun 5, 2023
…ware-mansion#3849)

<!-- Thanks for submitting a pull request! We appreciate you spending
the time to work on these changes. Please follow the template so that
the reviewers can easily understand what the code changes affect. -->

## Summary

<!-- Explain the motivation for this PR. Include "Fixes #<number>" if
applicable. -->
software-mansion#3824 introduces a bug with how we register ancestors of views with
`exiting` animations.
When a tree with `exiting` views is reattached to the native view
hierarchy, we don't register the ancestors of that tree as ancestors of
exiting subviews. This may cause issues with deleting these views early,
while there're still `exiting` animations running inside them.

## Test plan

<!-- Provide a minimal but complete code snippet that can be used to
test out this change along with instructions how to run it and a
description of the expected behavior. -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants