[HOLD for payment 2023-06-02] [$1000] Switching between windows takes cell pointer to unpredictable position in the new magic code input field

[kavimuru]

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. Navigate to sign in page
2. Enter email & click on ‘Continue’ button
3. Open email in new window
4. Open magic code email
5. Open the window where expensify app is opened
6. Enter two or more magic code digits
7. Open the window where email is opened
8. Open the windows where expensify app is opened again
9. Enter more magic code digits

Expected Result:

Cell pointer moves to unpredictable position

Actual Result:

Cell pointer should remain at the position where we left of entering magic code

Workaround:

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

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.9.4
Reproducible in staging?: y
Reproducible in production?: y
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

Recording.465.mp4

2023-05-03.03.22.29.mp4

Expensify/Expensify Issue URL:
Issue reported by: @Natnael-Guchima
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1683073996655359

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~018aab7f6c72d1c7ad
• Upwork Job ID: 1657419055620501504
• Last Price Increase: 2023-05-13

[MelvinBot]

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

[MelvinBot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[alexpensify]

I'm catching up from being OOO on Friday and Monday, I'll try to test this one soon.

[aimane-chnaif]

I suggest to hold this for #18398 where MagicCodeInput component is being refactored to functional component.

[alexpensify]

Thank you for flagging, I will review that GH.

[alexpensify]

Thank you @aimane-chnaif for the update. I'm putting this one on hold.

[alexpensify]

Still on hold

[alexpensify]

Still on hold

[Natnael-Guchima]

@alexpensify this #18398 refractor seems to be completed and deployed to staging.
And the behavior still holds.

2023-05-11.17.31.28.mp4

cc: @aimane-chnaif