Skip to content

[HOLD for payment 2024-07-24] [$250] Connect bank - "-1" is pre-filled for the tax ID number when connecting a new bank account #45073

Closed

Description

@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!


Version Number: 9.0.5-2
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Action Performed:

  1. Navigate to staging.new.expensify.com
  2. Create a workspace and enable workflows
  3. Go through connecting a bank account flow up until the fourth step where it requires you for the tax ID number

Expected Result:

The input field should be empty

Actual Result:

The input field has a pre-filled value of "-1"

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

15!image

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~016ff97d1a1bc0b4b8
  • Upwork Job ID: 1811441687713769949
  • Last Price Increase: 2024-07-11
  • Automatic offers:
    • suneox | Reviewer | 103085245
    • Krishna2323 | Contributor | 103085246
Issue OwnerCurrent Issue Owner: @RachCHopkins

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jul 9, 2024
  2. melvin-bot commented on Jul 9, 2024

    @melvin-bot

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

  3. lanitochka17 commented on Jul 9, 2024

    @lanitochka17
    Author

    @RachCHopkins FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

  4. Krishna2323 commented on Jul 9, 2024

    @Krishna2323
    Contributor

    Proposal

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

    Connect bank - "-1" is pre-filled for the tax ID number when connecting a new bank account

    What is the root cause of that problem?

    The default value of defaultCompanyTaxId is -1.

    const defaultCompanyTaxId = reimbursementAccount?.achData?.companyTaxID ?? '-1';
    const bankAccountID = reimbursementAccount?.achData?.bankAccountID ?? -1;
    const shouldDisableCompanyTaxID = !!(bankAccountID && defaultCompanyTaxId && reimbursementAccount?.achData?.state !== 'SETUP');

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

    I think this PR mistakenly changed the default value of defaultCompanyTaxId and bankAccountID. We should revert the changes in TaxIdBusiness and also look for other files which might have been affected. I think we should only default to -1 when accessing from a value from onyx.

    What alternative solutions did you explore? (Optional)

    1. If we need -1 as default for determining shouldDisableCompanyTaxID value, we can directly default it when accessing it in shouldDisableCompanyTaxID or

    2. We can use reimbursementAccount?.achData?.companyTaxID for defaultValue prop value.

    3. Remove -1 and add empty string if needed.

    4. Remove the default value (??) from bankAccountID & defaultCompanyTaxId.

  5. RachCHopkins commented on Jul 10, 2024

    @RachCHopkins
    Contributor

    Clearly reproducible!

    image

    @blimpich can I get you to take a look at this? Looks like you were on that PR where this crept in? Should this be an internal or external fix?

  6. blimpich commented on Jul 10, 2024

    @blimpich
    Contributor

    @kubabutkiewicz can you take a look at this and see if there was a mistake that we made in #42634?

  7. kubabutkiewicz commented on Jul 11, 2024

    @kubabutkiewicz
    Contributor

    @blimpich yeah this comes from #42634 PR

  8. blimpich commented on Jul 11, 2024

    @blimpich
    Contributor

    Sweet, lets make this open to contributors then and get it fixed.

  9. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jul 11, 2024
  10. changed the title [-]Connect bank - "-1" is pre-filled for the tax ID number when connecting a new bank account[/-] [+][$250] Connect bank - "-1" is pre-filled for the tax ID number when connecting a new bank account[/+] on Jul 11, 2024
  11. melvin-bot commented on Jul 11, 2024

    @melvin-bot
  12. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jul 11, 2024
  13. 16 remaining items

  14. changed the title [-][$250] Connect bank - "-1" is pre-filled for the tax ID number when connecting a new bank account[/-] [+][HOLD for payment 2024-07-24] [$250] Connect bank - "-1" is pre-filled for the tax ID number when connecting a new bank account[/+] on Jul 17, 2024
  15. melvin-bot commented on Jul 17, 2024

    @melvin-bot

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

  16. melvin-bot commented on Jul 17, 2024

    @melvin-bot

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

    If no regressions arise, payment will be issued on 2024-07-24. 🎊

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

  17. melvin-bot commented on Jul 17, 2024

    @melvin-bot

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@suneox] The PR that introduced the bug has been identified. Link to the PR:
    • [@suneox] 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:
    • [@suneox] A discussion in #expensify-bugs 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:
    • [@suneox] Determine if we should create a regression test for this bug.
    • [@suneox] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
    • [@RachCHopkins] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  18. suneox commented on Jul 20, 2024

    @suneox
    Contributor
  19. RachCHopkins commented on Jul 25, 2024

    @RachCHopkins
    Contributor

    All contracts paid via Upwork!

  20. RachCHopkins commented on Aug 12, 2024

    @RachCHopkins
    Contributor

    Payment Summary:

    Contributor: @Krishna2323 paid $250 via Upwork

    Contributor+: @suneox paid $250 via UpWork

    Upwork job here

    Contributor has been paid, the contract has been completed, and the Upwork post has been closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions