Skip to content

[HOLD for payment 2024-07-22] [HOLD for payment 2024-07-17] [$250] [HOLD 36648] Wallet - Idology questions flow does not start after entering bank account details #44462

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.2-0
Reproducible in staging?: Y
Reproducible in production?: Unable to check
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4673461
Email or phone of affected tester (no customers): applausetester+062524dr002@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. Open app or go to staging.new.expensify.com
  2. Log in with any account without a wallet configured
  3. Go to Settings > Wallet
  4. Click on 'Enable wallet'
  5. Follow the bank account flow until the final 'Confirm' page (using Bank: Chase / Account: 1111 / First name: Alberta / Last name: Bobbeth / SSN: 3333)
  6. Tap 'Confirm' button

Expected Result:

Idology questions flow has started

Actual Result:

Nothing happens after pressing the 'Confirm' button. Idology questions flow does not start

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

Bug6524686_1719361533938.Desktop-Wallet-No-idology.questions-flow.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~014deaa2c3f332d2e4
  • Upwork Job ID: 1806785838003619663
  • Last Price Increase: 2024-06-28
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @OfstadC
Issue OwnerCurrent Issue Owner: @OfstadC

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Jun 26, 2024
  2. melvin-bot commented on Jun 26, 2024

    @melvin-bot

    Triggered auto assignment to @thienlnam (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  3. melvin-bot commented on Jun 26, 2024

    @melvin-bot

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

  4. github-actions commented on Jun 26, 2024

    @github-actions
    Contributor

    👋 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.
  5. lanitochka17 commented on Jun 26, 2024

    @lanitochka17
    Author

    We think that this bug might be related to #vip-vsp

  6. lanitochka17 commented on Jun 26, 2024

    @lanitochka17
    Author

    @thienlnam @OfstadC 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

  7. thienlnam commented on Jun 26, 2024

    @thienlnam
    Contributor

    It seems like this failed because of a non-matching SSN (logs)

    I wonder if this was updated for our test bank account recently but it doesn't seem to be from any recent changes

  8. 34 remaining items

  9. melvin-bot commented on Jul 10, 2024

    @melvin-bot

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

  10. melvin-bot commented on Jul 10, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.5-13 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-17. 🎊

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

    • @Pujan92 does not require payment (Contractor)
    • @koko57 does not require payment (Contractor)
  11. melvin-bot commented on Jul 10, 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:

    • [@Pujan92] The PR that introduced the bug has been identified. Link to the PR:
    • [@Pujan92] 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:
    • [@Pujan92] 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:
    • [@Pujan92] Determine if we should create a regression test for this bug.
    • [@Pujan92] 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.
    • [@OfstadC] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  12. OfstadC commented on Jul 10, 2024

    @OfstadC
    Contributor

    Thanks @Pujan92 ! Could you complete the BZ checklist when you have a chance? Thanks! 😃

  13. Pujan92 commented on Jul 10, 2024

    @Pujan92
    Contributor

    @OfstadC I believe that will be handled in the parent issue #36648

  14. OfstadC commented on Jul 11, 2024

    @OfstadC
    Contributor

    Ah okay! 😅 Thanks @Pujan92 !

  15. changed the title [-][HOLD for payment 2024-07-17] [$250] [HOLD 36648] Wallet - Idology questions flow does not start after entering bank account details[/-] [+][HOLD for payment 2024-07-22] [HOLD for payment 2024-07-17] [$250] [HOLD 36648] Wallet - Idology questions flow does not start after entering bank account details[/+] on Jul 15, 2024
  16. melvin-bot commented on Jul 15, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.6-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-22. 🎊

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

    • @Pujan92 does not require payment (Contractor)
    • @koko57 does not require payment (Contractor)
  17. melvin-bot commented on Jul 15, 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:

    • [@Pujan92] The PR that introduced the bug has been identified. Link to the PR:
    • [@Pujan92] 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:
    • [@Pujan92] 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:
    • [@Pujan92] Determine if we should create a regression test for this bug.
    • [@Pujan92] 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.
    • [@OfstadC] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  18. OfstadC commented on Jul 17, 2024

    @OfstadC
    Contributor

    Closing this out -

    No payment needed per:

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

    @Pujan92 does not require payment (Contractor)
    @koko57 does not require payment (Contractor)

    And checklist should be covered here

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.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributors

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions