-
Notifications
You must be signed in to change notification settings - Fork 25.1k
Closed as not planned
Labels
Component: ScrollViewNeeds: Triage 🔍Platform: AndroidAndroid applications.Android applications.Platform: LinuxBuilding on Linux.Building on Linux.StaleThere has been a lack of activity on this issue and it may be closed soon.There has been a lack of activity on this issue and it may be closed soon.
Description
Description
When trying to scroll beyond the top and the bottom of the ScrollView the window "bounces" and moves in the opposite direction.
This leads to an unpleasant user experience and an unpredictable interaction with the UI.
Version
0.67.3
Output of npx react-native info
System:
OS: Linux 5.15 Manjaro Linux
CPU: (12) x64 AMD Ryzen 5 5600X 6-Core Processor
Memory: 551.49 MB / 15.61 GB
Shell: 5.1.16 - /bin/bash
Binaries:
Node: 14.18.1 - ~/.nvm/versions/node/v14.18.1/bin/node
Yarn: 1.22.17 - /usr/bin/yarn
npm: 6.14.15 - ~/.nvm/versions/node/v14.18.1/bin/npm
Watchman: Not Found
SDKs:
Android SDK: Not Found
IDEs:
Android Studio: AI-211.7628.21.2111.8139111
Languages:
Java: 11.0.13 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.67.3 => 0.67.3
npmGlobalPackages:
*react-native*: Not Found
Steps to reproduce
Create a ScrollView with enough content to scroll and build for an APK for Android
test with Android version 10 or above.
scrollview-bug.mp4
I tested on Android 10 and 11 devices and the issue persists
However, on older Android 7 devices and the component works as intended.
Snack, code example, screenshot, or link to a repository
Expo snack example https://snack.expo.dev/@oples/scroll-view-example it's possible to reproduce the bug in the appetize.io Android 10 emulator.
Metadata
Metadata
Assignees
Labels
Component: ScrollViewNeeds: Triage 🔍Platform: AndroidAndroid applications.Android applications.Platform: LinuxBuilding on Linux.Building on Linux.StaleThere has been a lack of activity on this issue and it may be closed soon.There has been a lack of activity on this issue and it may be closed soon.