Modal closing caused Animated childs back to start value of animation

[NguyenHoangMinhkkkk]

Description:

• Modal closing caused Animated childs back to start value of animation.
• Animating to translate child component to some coordinates(x,y) and After setState to close modal, child components inside be back to previous position

React Native version:
System:
OS: macOS 10.15.3
CPU: (6) x64 Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz
Memory: 511.51 MB / 16.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 13.6.0 - /usr/local/bin/node
Yarn: 1.21.1 - /usr/local/bin/yarn
npm: 6.13.4 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
Android SDK:
API Levels: 16, 18, 19, 21, 22, 23, 24, 26, 27, 28, 29
Build Tools: 28.0.3, 29.0.2
System Images: android-19 | Google APIs Intel x86 Atom, android-21 | Google APIs Intel x86 Atom_64, android-23 | Google APIs Intel x86 Atom_64, android-27 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom_64
IDEs:
Android Studio: 3.5 AI-191.8026.42.35.6010548
Xcode: 11.3.1/11C504 - /usr/bin/xcodebuild

Steps To Reproduce

• Toggle on modal
• Translate child component
• Toggle off modal
• See what happens at closing moment

Expected Results

Child component's animation position stand at it's position on closing modal

Snack, code example, screenshot, or link to a repository:

[NguyenHoangMinhkkkk]

I found that this issue only happen when childs component's animation useNativeDriver:true.
So, anything works properly with useNativeDriver:false at child components.

• but, why?

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

[stale]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.