react-native-snap-carousel: Swiper freezes on second slide.
Is this a bug report, a feature request, or a question?
Bug report
Have you followed the required steps before opening a bug report?
- I have read the guidelines regarding bug report.
- I have reviewed the documentation in its entirety, including the dedicated documentations 📚.
- I have searched for existing issues and made sure that the problem hasn’t already been reported.
- I am using the latest plugin version.
- I am following the issue template closely in order to produce a useful bug report.
Have you made sure that it wasn’t a React Native bug?
Yes
Is the bug specific to iOS or Android? Or can it be reproduced on both platforms?
Both iOS and Android
Is the bug reproductible in a production environment (not a debug one)?
Yes.
Environment
software | version |
---|---|
react | 16.5.0 |
react-native | 0.56.1 |
react-native-snap-carousel | 3.7.3 |
Target | Android (6.0) |
Target | iOS (9.0) |
Expected Behavior
The swiper should be swipeable. If downgrading and fixing to react-native-snap-carousel 3.7.2
it works as expected.
Actual Behavior
After updating the yarn.lock
file, the swiper broke in our app. We could swipe to the second slide, but then it froze. We could neither slide forward nor backward. Interactions (e.g. links) on the current slide still work.
Reproducible Demo
Unfortunately I couldn’t reproduce this bug in a minimal app. Everything worked fine. I’ll continue to work on a reproduction and update this issue.
Does anybody else have similar problems or a setup where the carousel breaks with the latest react-native-snap-carousel
version? I’d appreciate if someone could confirm the issue or help me resolve it.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 20 (9 by maintainers)
For anyone who still seems to have a similar issue,
removeClippedSubviews={false}
might solve your problem.@dpogoda Should be fixed in version
3.7.4
😉Well, I should have tested the PR myself… Ok, I’ll try and fix it as soon as I can.
Thanks for the feedback 😉
Hi @dpogoda,
The bug might be linked to PR #390. Does it work properly if you remove the added line?