-
Notifications
You must be signed in to change notification settings - Fork 431
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
onVisibleIndicesChanged stops working after X list items [Android and iOS] #334
Comments
Will it be possible to provide a repro on expo? That will help me look into this quickly. On my end it doesn't happen for such items. There was a recent bug discovered to items with 0 height but that doesn't seem relevant here. If you want to debug yourself look inside |
I observed skipped The progression of debugging:
I optimized the components via |
@naqvitalha onVisibleIndicesChanged triggers two times if scroll, I have 10 items in the array and I have full page item, I have set forceNonDeterministicRendering={true},
console logs
|
Hey @paddy57 did you get any solution for two time console? Also do you know how can we achieve this case : "I want those indexes which is visible atleast more than 50%" |
On a recyclerlistview, we're noticing that after the first 8 items are loaded each subsequent item no longer fires onVisibleIndicesChanged (on both iOS and Android).
We are noticing a few funny things using full screen width and height for list items so we're not sure if that might impact onVisibleIndicesChanged or not. Any tips for debugging would be most welcome. Why eight? we don't know. Sometimes it'll start working again but more often than not it won't fire after the first 8.
The list we have is designed to be a vertical swiping experience. Each item is swiped to by the user. This is to accommodate full screen captured video and images.
Data/layout provider
OnVisibleIndicesChanged logic:
Rowrenderer (the activitycomponent has height:screen.height set).
List
Notable libs
The text was updated successfully, but these errors were encountered: