-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Swiper cuts off after state update on another page #1215
Comments
the same problem - if I like the page and state updates, the screen changes the page on another one, but pagination stays the same. Then I swipe and see on the same pagination necessary liked screen. So once again, pagination stays the same. And then if there no more state updates, the swiper works as usual. |
Is there any solution to this issue? |
I just ran into this issue too and fixed it by using the current master ref in my package.json. Looks like this is fixed in master! |
Can you expand on changing the ref to master? Sorry i'm quiet new to this |
Sure! In my package.json I changed: |
still doesn't work |
Hi Guys, |
when is this thing going to get updated ?? |
@skv-headless @mohity7777 renderScrollView = pages => {
return (
<ScrollView
ref={this.refScrollView}
{...this.props}
{...this.scrollViewPropOverrides()}
contentContainerStyle={[styles.wrapperIOS, this.props.style]}
// try remove this line. or sync the state.offset with internal.offset.
// contentOffset={this.state.offset}
onScrollBeginDrag={this.onScrollBegin}
onMomentumScrollEnd={this.onScrollEnd}
onScrollEndDrag={this.onScrollEndDrag}
style={this.props.scrollViewStyle}
>
{pages}
</ScrollView>
)
} |
Actually doing the changes in node modules solved my issue. I just meant that why is this not there in latest release ? |
This solved it for me. Thank you! |
Thank you, this was a life-saver! |
You're a super-man! |
Sure! In my package.json I changed: |
After I swipe to the second page, if a state update occurs on the previous page, the current page gets drifted to the left. Is there any solution to this issue?
The text was updated successfully, but these errors were encountered: