[HOLD for payment 2024-08-05] [$250] Track Expense - Blue Border Appears on the Track Expense Button

[izarutskaya]

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: v9.0.8-1
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): abebemiherat@gmail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

1. Navigate to FAB > Track Expense.
2. Add an amount and press Enter to proceed.
3. Observe that a blue border appears on the Track Expense button.

Expected Result:

The blue border should not appear on the Track Expense button when Enter is pressed.

Actual Result:

A blue border appears on the Track Expense button when Enter is pressed.

Note: It is also reproducible on Submit expense flow

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

Bug6544741_1721198919290.Screen_Recording_2024-07-16_at_11.47.29_PM.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0137b996b36a246d89
• Upwork Job ID: 1813481853685332253
• Last Price Increase: 2024-07-17
• Automatic offers:
• akinwale | Reviewer | 103180951
• nkdengineer | Contributor | 103180952

[melvin-bot]

Triggered auto assignment to @CortneyOfstad (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Triggered auto assignment to @techievivek (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.

[izarutskaya]

We think this issue might be related to the #vip-vsb

[izarutskaya]

Production

bandicam.2024-07-17.10-19-43-201.mp4