Web - When "Pasting" a code in sign in menu, the code vanishes and/or flashes

[lanitochka17]

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. Access staging.new.expensify.com
2. Input an email address
3. Copy a code from email (It can be the right code or wrong code)
4. Pate the code

Expected Result:

The user expects that the code will show in the input field

Actual Result:

The code either flashes rapidly before signing into the account OR does not show at all if it is the incorrect code that is being pasted

Workaround:

Unknown

Platforms:

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

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.42.6

Reproducible in staging?: Yes

Reproducible in production?: No

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

Notes/Photos/Videos: Any additional supporting documentation

Bug6131970_When_pasting_the_code_it_either_flashes_or_disappears.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

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

[bernhardoj]

Dupe of #22963

[cead22]

Labeling daily since it looks like it's already being worked on

[jasperhuangg]

@cead22 I'm unable to reproduce this in our staging or production builds. Looks like it was fixed by #23023. Closing

Screen.Recording.2023-07-18.at.10.54.33.AM.mov