BA - Error message doesn't stop displaying instantly after valid data is entered in date field

[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.2.0
Reproducible in staging?: y
Reproducible in production?: not able to check production
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:

Pre-requisite: user must be logged in.

1. Go to Settings > Workspaces > Select Workspace > Bank Account.
2. Go trough the add bank account flow until you reach a page that you have to enter any date, like Company information or Personal Information.
3. Trigger the enter valid data error message on the date field (select the filed but do not select any date and move to another field).
4. Select a valid date.

Expected Result:

The error message should disappear instantly, like the other fields do.

Actual Result:

The error message doesn't stop displaying instantly after valid data is entered.

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

Bug6287443_1700671928440.Yanj6389_1_.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @thienlnam (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[thienlnam]

Looks like this is fixed when reverting #27670

[luacmartins]

Removing blocker label since we reverted the offending PR

[kowczarz]

I think as soon as #31612 will be fixed, this issue can disappear as well.

[kosmydel]

As @kowczarz said, this issue is resolved by this PR and probably was not related to reverting the focus trap.