You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No. I would wonder if there were many people with the problem but with gitHub not providing any feedback loop other than creating a issue, there doesn't seem to be any way to know if it was a mistake using this repository. I've used 4 different sliders like this, only this one seems not to use the native built in indexing but use a calculated offset. Since it works on the first 10 or so items in my array, but not on any further down the list, I am sure that this is a problem with the way the firstItem is being calculated and if so - should be a warning to only use this for iOS.
First small number of items will correctly pick the correct item.
Anything about 20 or so items in the array will NOT start with the correct index.
Expected Behavior
I expected when I send an array of data to the carousel that it would start at the correct item in the array. It does not. It does not work in production either. I would love to know if this is a known bug or issue.
Is this a bug report or a feature request?
Bug Report
Have you read the guidelines regarding bug report?
Yes
Have you read the documentation in its entirety?
Yes
Have you made sure that your issue hasn't already been reported/solved?
I didn't see it anywhere, other than the reference to the instability of the indexing on Android.
Is the bug specific to iOS or Android? Or can it be reproduced on both platforms?
Android
Is the bug reproductible in a production environment (not a debug one)?
Yes - built it in production mode.
Have you been able to reproduce the bug in the provided example?
No. I would wonder if there were many people with the problem but with gitHub not providing any feedback loop other than creating a issue, there doesn't seem to be any way to know if it was a mistake using this repository. I've used 4 different sliders like this, only this one seems not to use the native built in indexing but use a calculated offset. Since it works on the first 10 or so items in my array, but not on any further down the list, I am sure that this is a problem with the way the firstItem is being calculated and if so - should be a warning to only use this for iOS.
Environment
Environment:
React: 16.0.0
React native: 0.51
react-native-snap-carousel: 3.6.0
Target Platform:
Android (API 27)
Steps to Reproduce
Expected Behavior
I expected when I send an array of data to the carousel that it would start at the correct item in the array. It does not. It does not work in production either. I would love to know if this is a known bug or issue.
Actual Behavior
Very simple. Does NOT go to the index as sent in.
Reproducible Demo
The text was updated successfully, but these errors were encountered: