-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
Invariant Violation : Unable to find node on an unmounted component. #23790
Comments
T35574538 (the internal task) was closed in November 2018 as fixed. You're using React Native 0.57.1, which was released September 2018. I'm going to close this as resolved. |
Thank you @hramos, maybe you can remove the internal task as TODO in the code or indicate it is fixed by RN 0.XX. By the way which version of RN is it in November 2018 ? |
The latest stable release of React Native is 0.58, though we are about to release 0.59 this month. After following up regarding the removal of the TODO comment, the internal task was re-opened as it looks like it can be reproed on master. I'll re-open here until it's confirmed fixed. |
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. |
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. |
🐛 Bug Report
App crashes with "Invariant Violation : Unable to find node on an unmounted component." error message
To Reproduce
Scroll inside a VirtualizedList.
After some investigation inside VirtualizedList code, I noticed this comment in https://github.com/facebook/react-native/blob/8da1f1149f5ee9f8a75cbc8baac280c95585daa2/Libraries/Lists/VirtualizedList.js
Expected Behavior
Fix the TODO ;)
Code Example
Environment
The text was updated successfully, but these errors were encountered: