Scrollview w/ pagingEnabled instantly changing page on Android when scrolling fast

[mtnptrsn]

Is this a bug report?

Yes

Have you read the Contributing Guidelines?

Yes

Environment

Environment:
OS: macOS High Sierra 10.13.1
Node: 7.9.0
Yarn: 0.22.0
npm: 4.2.0
Watchman: 4.9.0
Xcode: Xcode 9.1 Build version 9B55
Android Studio: 2.3 AI-162.3934792

Packages: (wanted => installed)
react: 16.0.0 => 16.0.0
react-native: https://github.com/expo/react-native/archive/sdk-23.0.0.tar.gz => 0.50.3

Target Platform: iOS (11.2) & Android (8.0)

Steps to Reproduce

1. Create a scrollview with pagingEnabled, horizontal and 100% width & height
2. Populate the scrollview with more than 3 <View /> elements with device width and flex: 1 (so it takes up the whole height)
3. Scroll really quickly between those elements on Android
4. You'll now see an instant hop from one element to the other, without an animation
5. Do the same thing on iOS and it will be a smooth scroll animation

Expected Behavior

I expected it to be the same on Android as it is on iOS, a smooth scroll animation instead of instantly changing page.

Actual Behavior

Instantly switching page on Android (without any animation)

Video demonstration

Reproducible Demo

Expo snack

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions.

[Fsarmento]

I had the same problem using scrollview with pagingEnabled. Ended up using ViewPagerAndroid for android to have a smoother scrolling effect. However, it gives much more work since the scroll event props for ViewPagerAndroid.onPageScroll are "offset" and "position", not the same as in ScrollView.

[react-native-bot]

Thanks for posting this! It looks like you may not be using the latest version of React Native, v0.53.0, released on January 2018. Can you make sure this issue can still be reproduced in the latest version?

I am going to close this, but please feel free to open a new issue if you are able to confirm that this is still a problem in v0.53.0 or newer.

_{How to Contribute • What to Expect from Maintainers}

[scottmas]

Experiencing this in RN 55.4