Payments -Two options are hidden when you click on > button

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

---

Action Performed:

1. Go to staging.new.expensify,com
2. Log in with any account
3. Go to Profile - Settings
4. Select Payments
5. Click on > button

Expected Result:

Two options are visible when you click on > button

Actual Result:

Two options are hidden when you click on > button

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Web

Version Number: 1.1.57.12

Reproducible in staging?: Yes

Reproducible in production?: No

Email or phone of affected tester (no customers):

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Recording.376.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause

Slack conversation:

View all open jobs on GitHub

[OSBotify]

👋 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 @NikkiWines (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[NikkiWines]

Yeah, this is weird. Marking as external! Nvm it's a deploy blocker, looking into this!

[NikkiWines]

I think it's because of #8609. cc: @parasharrajat @thesahindia

I checked out the commit directly prior to the merge commit and it worked as expected:

[NikkiWines]

I'm not sure how to fix this off the top of my head and I'm OOO for most of today, so let's revert for now and re-introduce it with this edge case accounted for.

[thesahindia]

@NikkiWines, I had mentioned about this in #8609 (comment)
To get more info about this issue you can check this #7985 (comment)

[NikkiWines]

Ah, I must have missed that - thank you for the context @thesahindia.

If there's already a potential fix in the works I think in this case then it is ok to remove the deploy blocker label. Let's make sure to test this case in that PR as well. cc: @Julesssss since you just self-assigned #7985

[NikkiWines]

Oh oops, we can close this since the bug will be handed in #7985