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

Snaptoitem doesn't work with more than 10 elements? #513

Open
bishnudev opened this issue May 3, 2019 · 15 comments
Open

Snaptoitem doesn't work with more than 10 elements? #513

bishnudev opened this issue May 3, 2019 · 15 comments

Comments

@bishnudev
Copy link

Is this a bug report, a feature request, or a question?

Question

There're 11 cards in my snap carousel. When i try snapToItem(i) where i < 10, it works perfectly fine but when i try snapToItem(10), it just moves to the 10th card. Isn't it supposed to move to the 11th card since i'm passing a index of 10. Is there any kind of limit over number of cards in the snapcarousel?

@LimAlbert
Copy link

Hello,

I had the same issue and I solved it by using the initialNumToRender prop !
By default, all the slides are not rendered for optimization so I guess that's why snapToItem was not able to find the slide :)

@eggybot
Copy link

eggybot commented Jun 2, 2019

It looks like the new version 3.8.0 has a bug, I only have 3 items but snaptoitem works only for the first call/action then its not functioning, same with snaptonext and snaptoprev. I;m using the latest RN0.59.8

@LimAlbert
initialNumToRender didn't work for me

@cr1s3c
Copy link

cr1s3c commented Jun 5, 2019

@eggybot i have the same issue, do you have any solution?

@eggybot
Copy link

eggybot commented Jun 5, 2019

@cr1s3c
I revert back to version 3.7.5, will wait till this issue resolve.

@cr1s3c
Copy link

cr1s3c commented Jun 5, 2019

@eggybot thank you, after reverting to 3.7.5 and reverting react from 16.8.3 to 16.6.3 it is working again.

@bd-arc
Copy link
Contributor

bd-arc commented Jun 6, 2019

Well, I now need to find out which one of the PR I recently merged is responsible for that.

#443 is a strong candidate IMO. If someone has the time to test if reverting this fixes the issue, I'd really appreciate it.

@rafalzawadzki
Copy link

I have the same issue and going back to 3.7.5 did not solve the problem. React 16.8.3 and RN0.59.8.

@bd-arc I tested if reverting this on 3.8.0 solves the issue, but unfortunately seems not...

@eggybot
Copy link

eggybot commented Jun 7, 2019

@rafalzawadzki
try uninstall/install it works for me.

@hanwenbo
Copy link

@eggybot Thanks 3.7.5 for fixing my problem

@vittau
Copy link

vittau commented May 27, 2020

Any update on this?
I have a Carousel with almost 300 items, and it's simply impossible to set initialNumToRender that large with acceptable performance. :(

@bd-arc
Copy link
Contributor

bd-arc commented May 28, 2020

@vittau Have you given a try to version 4.0.0-beta.4?

We're now relying on FlatList's initialScrollIndex, which should help with large datasets.

@vittau
Copy link

vittau commented May 28, 2020

@vittau Have you given a try to version 4.0.0-beta.4?

We're now relying on FlatList's initialScrollIndex, which should help with large datasets.

Thank you! It really does work correctly now without having to set initialNumToRender. :)

@Navipro70
Copy link

Navipro70 commented Aug 31, 2021

Something interesting I meet when trying fix this problem. I have very loaded screen with carousel of video components and custom interface. When I snap from 1 video to 10+, slider stucks on 6-7th card, but when I set prop windowSize={SCREEN_WIDTH} bug disappeared and I successfully snap from 1 to 40 without stucks.

Tested on iPhone 11, iPhone 6s.

UPD: Yep since it's common flatlist, windowSize eats RAM

@dohooo

This comment was marked as spam.

@alirehmanappcrates
Copy link

I tried both windowSize and initialNumToRender props but still, it gets stuck on the 6th and 7th item if I call snapToItem(10+)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests