Carousel locks onto index 0 even when current index is non-zero

[with-a-k]

I have a sideswipe view that contains a data array that the user can add and remove items to. However, when I try sliding the view to another item in the array, the carousel locks itself to the item with index 0, even though the container's currentIndex state and the matching prop on the items themselves are some other index.

envinfo results:
System:
OS: Linux 4.4 Ubuntu 16.04.3 LTS (Xenial Xerus)
CPU: x64 Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
Memory: 5.82 GB / 15.89 GB
Shell: 4.3.48 - /bin/bash
Binaries:
Node: 8.9.1 - /usr/bin/node
npm: 6.2.0 - /usr/bin/npm
Watchman: 4.7.0 - /usr/local/bin/watchman
Utilities:
Make: 4.1 - /usr/bin/make
GCC: 5.4.0 - /usr/bin/gcc
Git: 2.7.4 - /usr/bin/git
IDEs:
Nano: 2.5.3 - /bin/nano
Vim: 7.4 - /usr/bin/vim
Languages:
Bash: 4.3.48 - /bin/bash
Java: 1.8.0 - /usr/bin/javac
Perl: 5.22.1 - /usr/bin/perl
Python: 2.7.12 - /usr/bin/python
Ruby: 2.2.7 - /usr/share/rvm/rubies/ruby-2.2.7/bin/ruby
Databases:
SQLite: 3.11.0 - /usr/bin/sqlite3
Browsers:
Chrome: 62.0.3202.94

Please make sure these boxes are checked before submitting your issue!

• [ X ] envinfo results
• [ X ] I created a reproduction example here (if bug related)

[GelsonBlaze]

I have the same problem and would like a solution as well. Resetting the currentIndex doesn't work.

Edit: Use an if statement. If currentIndex > 0 u reset it to 0 on item remove or add.

[kkemple]

currentIndex needs to be a prop on the SideSwipe component, not it's children, it is using default currentIndex of 0, move that prop up to sideswipe component and should work!

[nilsbacke-ef]

Hello, I am still having this issue. I'm using Typescript, and I cannot add the currentIndex prop to the SideSwipe component because it does not exist. The currentIndex prop in the renderItem callback is always returning 0.