[HOLD for payment 2024-06-20] [$250] Web - IOU - Currency listing page displays empty when clicked on currency

[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: 1.4.63-0
Reproducible in staging?: y
Reproducible in production?: n
Issue found when executing PR: #38892
Issue reported by: Applause - Internal Team

Action Performed:

1. Tap on a chat --- tap the FAB > track expense
2. Enter an amount > change currency to RP> tap next
3. Tap track expense (add a merchant when required)
4. Tap on newly created expense to open expense details
5. Tap amount to edit the currency
6. Notice the currency page takes a minute to load

Expected Result:

Currency listing page should be displayed with available currencies

Actual Result:

The currency listing page is displayed empty. When user taps on screen the currency list appears

Workaround:

n/a

Platforms:

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

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

Screenshots/Videos

Add any screenshot/video evidence

RPReplay_Final1714710485.MP4

Bug6453814_1713455722598.Screen_Recording_2024-04-18_at_18.53.39.1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~015e149d6e5bb867bf
• Upwork Job ID: 1782471211809525760
• Last Price Increase: 2024-05-22
• Automatic offers:
• nkdengineer | Contributor | 102517477

Issue Owner

Current Issue Owner: @Christinadobrzyn

[melvin-bot]

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

[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.

[kbecciv]

Issue is reproduced Only on MacOS/ Safari

[deetergp]

Wow, that really is specific to Safari! It works just fine in Chrome. I wonder if this TS migration isn't the culprit #40100

[deetergp]

This seems pretty edge-case-y. I'm going to demote it as not-a-blocker.