[HOLD for payment 2024-12-09] [$250] iOS - Accounting - Confirm button jumps when entering user ID for Sage Intacct

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.59.0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5195617
Issue reported by: Applause Internal Team

Action Performed:

Precondition: user has saved credentials

1. Open the app and log in
2. Create a workspace if there is no any
3. Navigate to the workspace settings > More features and enable the Accounting option
4. Open Accounting and select Intacct
5. Upgrade the policy if it has not been done yet
6. Proceed to the step to enter credentials
7. Tap the user ID field and start entering the credentials

Expected Result:

The Confirm button does not jump

Actual Result:

The Confirm button jumps when entering user ID. It does not happen when entering a password even though the password auto-fill is present.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6658415_1731037676511.IMG_0873.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021859980122209615794
• Upwork Job ID: 1859980122209615794
• Last Price Increase: 2024-11-22
• Automatic offers:
• suneox | Reviewer | 105074090
• huult | Contributor | 105074091

Issue Owner

Current Issue Owner: @johncschuster

[melvin-bot]

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

[IuliiaHerets]

Issue is repro on newest iOS devices (iPhone 15 Pro Max and iPhone 16)

[twilight2294]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Confirm button jumps when entering user ID for Sage Intacct

What is the root cause of that problem?

We do not pass any ref to the InputWrapper this makes the state to always change.

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

Pass a ref to InputWrapper:

    const {inputCallbackRef} = useAutoFocusInput();
    
            <InputWrapper
                InputComponent={TextInput}
                inputID={formItem}
                label={translate(`common.${formItem}`)}
                aria-label={translate(`common.${formItem}`)}
                role={CONST.ROLE.PRESENTATION}
                spellCheck={false}
                secureTextEntry={formItem === INPUT_IDS.PASSWORD}
                ref={inputCallbackRef}
            />

What alternative solutions did you explore? (Optional)

[melvin-bot]

@slafortune Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[truph01]

Proposal

Please re-state the problem that we are trying to solve in this issue.

The Confirm button jumps when entering user ID. It does not happen when entering a password even though the password auto-fill is present.

What is the root cause of that problem?

It's an issue with the Passwords option in the Keyboard toolbar. We already notice it in facebook/react-native#39411 (comment)

We should fix it since it can affect on users experience (button jumps unexpectedly on non-password input)

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

We can use textContentType='oneTimeCode'

textContentType='oneTimeCode'

What alternative solutions did you explore? (Optional)

We can show the Confirm button right below the inputs by updating the styles.justifyContentEnd here

App/src/components/FormAlertWithSubmitButton.tsx

Line 100 in 5b1ee3f

containerStyles={[styles.justifyContentEnd, safePaddingBottomStyle, containerStyles]}

            containerStyles={[shouldShowConfirmButtonAtTheEnd && styles.justifyContentEnd, safePaddingBottomStyle, containerStyles]}

Screen.Recording.2024-11-11.at.23.52.49.mov

[melvin-bot]

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

[melvin-bot]

@slafortune 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[melvin-bot]

@slafortune 10 days overdue. Is anyone even seeing these? Hello?

[melvin-bot]

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

[abekkala]

Stevie has been and will be ooo - reapplying label

[melvin-bot]

@johncschuster this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021859980122209615794

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.69-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• fix resolve confirm button position issue #53131

If no regressions arise, payment will be issued on 2024-12-09. 🎊

For reference, here are some details about the assignees on this issue:

• @suneox requires payment automatic offer (Reviewer)
• @huult requires payment automatic offer (Contributor)

[melvin-bot]

@suneox @johncschuster @suneox The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[johncschuster]

BugZero Checklist:

• [Contributor] Classify the bug:

Bug classification

Source of bug:

• 1a. Result of the original design (eg. a case wasn't considered)
• 1b. Mistake during implementation
• 1c. Backend bug
• 1z. Other:

Where bug was reported:

• 2a. Reported on production
• 2b. Reported on staging (deploy blocker)
• 2c. Reported on both staging and production
• 2d. Reported on a PR
• 2z. Other:

Who reported the bug:

• 3a. Expensify user
• 3b. Expensify employee
• 3c. Contributor
• 3d. QA
• 3z. Other:

• [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

  Link to comment:

• [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

  Link to discussion:

• [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

Regression Test Proposal Template

• [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

  Link to issue:

Regression Test Proposal

Precondition:

Test:

Do we agree 👍 or 👎

[suneox]

BugZero Checklist:

• [Contributor] Classify the bug:

Bug classification

Source of bug:

• 1a. Result of the original design (eg. a case wasn't considered)
• 1b. Mistake during implementation
• 1c. Backend bug
• 1z. Other: Existing issue on iOS

Where bug was reported:

• 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
• 2b. Reported on staging (eg. found during regression or PR testing)
• 2d. Reported on a PR
• 2z. Other:

Who reported the bug:

• 3a. Expensify user
• 3b. Expensify employee
• 3c. Contributor
• 3d. QA
• 3z. Other:

• [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

  Link to comment: This issue related to ios issue, so we don’t have an offending PR.

• [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

  Link to discussion: N/A

• [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
  N/A: It isn't an impactful bug

[johncschuster]

Payment has been issued. Thanks for your contributions! 🎉