-
Notifications
You must be signed in to change notification settings - Fork 24.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
[FlatList] Android: onMomentumScrollEnd doesn't trigger when use scrollToOffset #21718
Comments
Can you run If you believe this information is irrelevant to the reported issue, you may write |
did anyone have check this issue? just let me know there is somebody following this. Or, maybe some of you can tell me that's not an issue with react-native itself. Thanks! |
I am also currently having this issue with react native 0.57.5 |
ANyone has a workaround for this issue? |
+1 |
Having this issue as well. |
+1 on react-native 0.57.8v |
I was running into this issue also on 0.57.1. In my case, I was trying to use the scrollTo method on a Scroll View. I wanted to trigger something after scrolling to a specific location on the screen. I was able to use the onScroll prop to achieve this 😄
|
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions. |
I am also currently having this issue with react native 0.59 |
I am also currently having this issue with react native 0.61.2 |
I feel really bad to use scrollview in react-native.Another bug,onMomentumScrollEnd not work when |
I faced with it. I also use horizontal FlatList. |
I accidentally found a solution for myself. I wrapped every FlatList item in TouchableOpacity. |
Same here |
Still an issue on 0.67.4. I faced it using |
same issue |
still exists pls fix |
still have this issue in RN 0.66 |
Facing this issue today please fix |
Same here |
same here |
still an issue on 71.7 ... onmomentumscrollend is not called when using scrollTo and scrollToIndex |
+1 |
1 similar comment
+1 |
Is it related maybe? 681b35d |
Well, 5 years have passed, and the problem is still relevant. I think it's a good reason for me to switch to learning Kotlin. Thank you for the time spent learning Facebook/React Native. |
Here is a reproducible repository : https://github.com/dayze/eventOnMomuntumScrollEnd |
|
1 similar comment
|
Five years and counting... |
wow... this is still an issue? Stuff like this needs to be addressed maybe not instantly, but 4 years later this cannot be an issue if React Native must survive. |
yes... i tested it with reanimated's useSrollHandler
and sadly it's not working |
I've found this to be an issue also on the |
any update in this?? |
I thought I was alone, I can see the bug in version |
@raajnadar why do you think so? |
This commit was picked and released on |
@raajnadar unfortunately it's about a different issue #32235. It shouldn't have any effect on this one. |
I can confirm this bug is also present on the React Native Web |
I got the same issue. In RN 0.74. |
Are there any workarounds to address this? Unfortunately it's still present on RN |
Environment
React Native Environment Info:
System:
OS: macOS High Sierra 10.13.6
CPU: x64 Intel(R) Core(TM) i5-5675R CPU @ 3.10GHz
Memory: 60.77 MB / 8.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 8.11.1 - /usr/local/bin/node
Yarn: 1.9.4 - /usr/local/bin/yarn
npm: 5.6.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.0, macOS 10.14, tvOS 12.0, watchOS 5.0
IDEs:
Android Studio: 3.0 AI-171.4443003
Xcode: 10.0/10A255 - /usr/bin/xcodebuild
npmPackages:
react: 16.5.0 => 16.5.0
react-native: 0.57.2 => 0.57.2
Description
onMomentumScrollEnd doesn't trigger when use
scrollToOffset
in Android.And in iOS it works.
also i find that other methods e.g. scrollToIndex, have the same issue.
Reproducible Demo
The text was updated successfully, but these errors were encountered: