Split - List does not scroll up after selecting a split participant

[kbecciv]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: v1.4.33-3
Reproducible in staging?: y
Reproducible in production?: n
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
Expensify/Expensify Issue URL:
Issue reported by: Applause- Internal Team
Slack conversation:

Action Performed:

1. Click FAB > Request money.
2. Enter amount > Next.
3. Scroll down and click Split next to user.
   Note that the list does not scroll up.

Expected Result:

The list will scroll up each time after selecting a split participant.

Actual Result:

The list does not scroll up after selecting a split participant.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6360832_1706617994505.20240130_133824.mp4

View all open jobs on GitHub

[kbecciv]

We think that this bug might be related to #vip-bills
CC @davidcardoza

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

Triggered auto assignment to @johnmlee101 (Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[neonbhai]

Not reproducible on latest main:

Screen.Recording.2024-01-30.at.6.59.43.PM.mov

[mkhutornyi]

Dupe of #35374, #35396
This was fixed in v1.4.33-4

[francoisl]

Confirmed it's working fine on v1.4.33-4, closing.