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
On iOS with Expo SDK 52, using the swipe-back gesture results in the following critical issue:
The last card animates back correctly.
Immediately after, the swiper skips an additional card backward without animation.
The swiper becomes unresponsive to further interactions.
NOTE: This happens regardless of the infinite prop value. If the swiper is on the first card, swiping back unexpectedly takes it to the last card instead of stopping at the beginning. This severely impacts usability on iOS.
Steps to Reproduce:
Swipe a card back using the swipe-back gesture.
Observe that the card animates back correctly.
Notice that it skips another card backward without animation and the swiper becomes unresponsive.
Expected Behavior:
The swiper should stop at the previous card with no unexpected jumps and remain responsive to further actions.
This is a critical bug for swipe-back functionality. Any help or fix would be greatly appreciated!
If needed, I can provide additional context or examples to help debug this issue.
On iOS with Expo SDK 52, using the swipe-back gesture results in the following critical issue:
NOTE: This happens regardless of the infinite prop value. If the swiper is on the first card, swiping back unexpectedly takes it to the last card instead of stopping at the beginning. This severely impacts usability on iOS.
Steps to Reproduce:
Expected Behavior:
The swiper should stop at the previous card with no unexpected jumps and remain responsive to further actions.
Environment:
Expo SDK: 52
Platform: iOS
Library Version: react-native-deck-swiper v2.0.17
This is a critical bug for swipe-back functionality. Any help or fix would be greatly appreciated!
If needed, I can provide additional context or examples to help debug this issue.
Code example:
The text was updated successfully, but these errors were encountered: