-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Android - Distance - Scrolling doesn't work when the number of waypoints increases #27382
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @NikkiWines ( |
Yeah looks like it's almost certainly tied to #27076 since that modified scrolling for multiple waypoints. cc: @jjcoffee @arosiclair |
@arosiclair was able to reproduce this on v1.3.68-17 (yesterday's deploy) so this isn't actually a blocker and #27076 isn't the root cause. This isn't a blocker, but will continue to look into to see if we can find the root cause for it. |
ProposalPlease re-state the problem that we are trying to solve in this issue.Can't scroll the waypoints list on Android only. What is the root cause of that problem?In the distance page, we have a nested ScrollView. One for the whole page, and one for the waypoint list. On Android, we are unable to scroll the nested ScrollView. This can be reproduced in a fresh new react native project. This nested scrolling issue doesn't happen on iOS as nested scrolling is supported by default. This issue starts to happen after we wrap the whole page with a ScrollView What changes do you think we should make in order to solve the problem?To support nested scrolling on Android too, set App/src/components/DistanceRequest.js Lines 172 to 181 in b11bddc
|
@bernhardoj's root cause is correct. It's scrolling limit in android. |
Ah cool, thank you for the investigation and determining that it's a regression of #26728. @hayata-suenaga tagging you since you're the internal eng/ for that PR, do you want to handle this as a regression or shall we handle this as a separate issue and start looking at proposals? |
thank you for letting me know about this issue Nikki We can actually close this issue as we're making an UI change here and making the waypoint list not scrollable |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Issue found when executing PR #27076
Action Performed:
Expected Result:
User is able to scroll up to input stops
Actual Result:
User is unbale to scroll up
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.69-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Bug6199317_27076_Android_.mp4
Not reproducible in Production
Screen_Recording_20230914_003820_New.Expensify.mp4
Expensify/Expensify Issue URL:
Issue reported by: @situchan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1694021625336179
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: