Can you run react-native info and edit your issue to include these results under the Environment section?

If you believe this information is irrelevant to the reported issue, you may write [skip envinfo] under Environment to let us know.

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 😄

onScroll(event) {
     if (event.nativeEvent.contentOffset.y === this.targetScreenOffsetY) {
        this.doSomething();
     }
}

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
@joseph-perez thanks for workaround!

I feel really bad to use scrollview in react-native.Another bug,onMomentumScrollEnd not work when
scroll slowly on ios.

I faced with it. I also use horizontal FlatList. onMomentumScrollEnd very often not called if stop scroll with small velocity.

I accidentally found a solution for myself. I wrapped every FlatList item in TouchableOpacity.

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

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
I'll try to look into it

Five years and counting...
The problem still exists :(

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

useAnimatedScrollHandler({
onMomentumEnd: (event) => {
        console.log('hello')
      },
})

and sadly it's not working

I've found this to be an issue also on the ScrollView component, I've experienced this happening in RN 0.71 on Android API's 31-33 (Android 12 & 13) on both physical devices and the emulators.

any update in this??

I thought I was alone, I can see the bug in version 0.73.6 also, I think this will be solved in the next major release of the new architecture.

I think this will be solved in the next major release of the new architecture.

@raajnadar why do you think so?

@dimaportenko 681b35d

This commit was picked and released on 0.74.0, waiting for expo SDK 51 to test and confirm

@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 ~0.19.6

I got the same issue. In RN 0.74.

Are there any workarounds to address this? Unfortunately it's still present on RN 0.76.
EDIT: Looks like there's a PR here, but it's been marked as stale..

This should be fixed by #45187. I've made a few changes internally and I hope to land it this week

Great news! c69e330 has just landed, containing the fix. The branch cut for RN 0.77 is scheduled in ~2 weeks and this will go out in that version. I'm also publishing a few fixes on the iOS side to align expectations for when these events fire (#47471 and #47468 if ya want to track). In any case, these commits will be tagged with the versions they are part of.

I'm going to close this issue out for now. Special thanks to @Biki-das for the initial fix. Note that this fix does not contain support for performance testing (via FpsListener), there's a separate batch of work currently in progress to add support.

Thanks you @Abbondanzo for completing the same, means a lot, looking forward to make react native better.