Step 4 of VBA flow has border radius issue.

[Luke9389]

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:

Break down in numbered steps

Go through the VBA flow until you hit step 4 and verify that you see this:

Expected Result:

Describe what you think should've happened

Looks reasonable ha

Actual Result:

Describe what actually happened

Looks like screenshot above.

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platform:

Where is this issue occurring?

• Web
• iOS
• Android
• Desktop App
• Mobile Web

Version Number:
Reproducible in staging?:
Reproducible in production?:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @Christinadobrzyn (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[Pujan92]

Proposal

If the border isn't required we can take that class out from the view

App/src/pages/ReimbursementAccount/ACHContractStep.js

Line 229 in 835e9d2

<View key={index} style={[styles.p5, styles.border, styles.mb2]}>

<View key={index} style={[styles.p5, styles.mb2]}>

Or if the border is required we can apply
borderRadius: variables.componentBorderRadius

App/src/styles/styles.js

Line 619 in 835e9d2

borderRadius: variables.buttonBorderRadius,

[Luke9389]

Hey y'all I've already spun up a fix for this. Sorry, I should have marked this internal.

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

Current assignee @Luke9389 is eligible for the Engineering assigner, not assigning anyone new.

[Christinadobrzyn]

Shouldn't there be a C+ assigned with this internal label? Removed and added it and nothing changed.

[francoisl]

Applause finished QAing #13298, closing this blocker.