after upgrade from version 5.4.25 to 6.6.1 the viewPager blocked the scroll of parent flatList in ios

[gallavie]

Environment

react-native 0.75
viewPager 6.6.1
ios 17.5

Description

i have flatlist and i render in header the viewPager.
when i use version 5.4.25 everything worked prefect in ios and android i can scroll the flatlist up and down from any where.
but after upgrade to version 6.6.1 the viewPager worked but i cant scroll the flatlist up or down from viewPager header.
is happen only in ios and i think is related to element UIPageViewController in ios.

Reproducible Demo

[ExxEss]

I got the same issue

[JavaGalaxy]

Encountered similar issue with scroll. had to downgrde to 6.1.4:
react-native-pager-view": "6.1.4",

[jacolack]

See #722

[FlashGameDev]

Running into the same issue. PagerView inside of a ScrollView consumes all vertical scrolling gestures/events. Even when setting PagerView to

orientation="horizontal"

Even if i disable ViewPager

scrollEnabled={false}

It still will not let the ScrollView get any vertical touch gestures. I tried downgrading to 6.1.4 and it won't compile with react 0.76.

Please help!!

[JavaGalaxy]

Running into the same issue. PagerView inside of a ScrollView consumes all vertical scrolling gestures/events. Even when setting PagerView to

orientation="horizontal"

Even if i disable ViewPager

scrollEnabled={false}

It still will not let the ScrollView get any vertical touch gestures. I tried downgrading to 6.1.4 and it won't compile with react 0.76.

Please help!!

I see you tried 6.1.4 with 0.76
The only thing worked for me was 6.1.4 with 0.76.3 ( I don't know if subversion makes any difference, but may be worth a shot?!)

[FlashGameDev]

I also tried 7.0.0-rc.0 suggested in another post. Both give me xcode compile errors on 0.76.5

/ios/Pods/Headers/Public/RCT-Folly/folly/Optional.h:667:10 'folly/experimental/coro/Coroutine.h' file not found

what I don't get is that there appears to be a fix by someone in 2023 and it was just never pulled in? This github has several recent issues with this exact problem.

#734 claims to fix it and the comments suggest that it does. I've never had to manually patch something before. I assume if I ever need to rebuild my node_modules from scratch that I have to reapply this fix each time?

Update: just tried to apply the patch but the code has changed so much since then it doesn't compile anymore. What a disaster.