Magic code input doesn't work if the user changes the focus by clicking on the magic code field bottom border.

[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. Open the desktop web.
2. Go to the sign-in page.
3. Enter the Email/Phone number.
4. Navigate to the Magic code page.
5. Click on the magic code field bottom border
6. Observe that the input in focused.
7. Try typing the magic code.

Expected Result:

The user should be able to enter the magic code when the input is focused.

Actual Result:

The input is focused, but the user isn't able to enter the 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.34-1
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

Screen.Recording.2023-06-26.at.3.20.52.PM.mov

Recording.1123.mp4

Expensify/Expensify Issue URL:
Issue reported by: @Tushu17
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1687772989682719

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

[kavimuru]

Proposal

What is the root cause of that problem?

The styling overflow: 'hidden' applied to the textInputContainer is causing a limitation in the required dimensions, resulting in an empty space below the TextInput component.

App/src/styles/styles.js

Line 866 in 9fc9f79

overflow: 'hidden',

What changes do you think we should make in order to solve the problem?

To resolve the issue of the empty space below the TextInput component, you can remove the overflow: 'hidden' styling from the textInputContainer.

    textInputContainer: {
        flex: 1,
        justifyContent: 'center',
        height: '100%',
        backgroundColor: 'transparent',
        borderBottomWidth: 2,
        borderColor: themeColors.border,
-       overflow: 'hidden',
    },

What alternative solutions did you explore? (Optional)

none

[melvin-bot]

@JmillsExpensify Eep! 4 days overdue now. Issues have feelings too...

[JmillsExpensify]

Slammed with bug reports. I'll close the loop on these today.

[melvin-bot]

@JmillsExpensify Huh... This is 4 days overdue. Who can take care of this?

[JmillsExpensify]

Alright, I'm coming back to this issue now and I'm able to input a number every time when using the physical keyboard, not the virtual keyboard show in the reproduction video.

[JmillsExpensify]

Here's a video.

Screen.Recording.2023-07-12.at.06.56.27.mov