Skip to content

[$500] Web - Workspace - It's not accepting the SSN for the first time #37442

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: 1.4.44.0
Reproducible in staging?: Y
Reproducible in production?: N
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
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Issue found when executing PR #29991

Action Performed:

  1. Login with expensify account
  2. Go to Settings > Wallet > Enable Wallet
  3. Go through Chase plaid verification flow
  4. Follow the flow until Additional details
  5. Fill the form with following data: First name: Alberta Last name: Bobbeth SSN: 3333 Any other information for the rest of the fields
  6. Press Save & continue

Expected Result:

It should accept it

Actual Result:

It's not accepting the SSN for the first time. I can continue after clicking on the button again

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

Bug6395828_1709136868318.bandicam_2024-02-27_19-32-36-367.mp4

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    ExternalAdded to denote the issue can be worked on by a contributor
    on Feb 28, 2024
  2. changed the title [-]Web - Workspace - It's not accepting the SSN for the first time[/-] [+][$500] Web - Workspace - It's not accepting the SSN for the first time[/+] on Feb 28, 2024
  3. melvin-bot commented on Feb 28, 2024

    @melvin-bot
  4. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Feb 28, 2024
  5. melvin-bot commented on Feb 28, 2024

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @getusha (External)

  6. github-actions commented on Feb 28, 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.
  7. melvin-bot commented on Feb 28, 2024

    @melvin-bot

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

  8. puneetlath commented on Feb 28, 2024

    @puneetlath
    Contributor

    I talked to @joekaufmanexpensify and we don't think this should block the deploy given it's current usage. But let's definitely get it fixed.

  9. 2 remaining items

  10. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 28, 2024
  11. melvin-bot commented on Feb 28, 2024

    @melvin-bot

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

  12. damadoko commented on Feb 28, 2024

    @damadoko

    I think the bug came from BE, the error was retrived from UpdatePersonalDetailsForWallet.

  13. roryabraham commented on Mar 5, 2024

    @roryabraham
    Contributor

    @lanitochka17 the email of the account the bug occurred on would be helpful here. Managed to see from the video that it's

    applausetester+0227rbt@applause.expensifail.com

  14. roryabraham commented on Mar 5, 2024

    @roryabraham
    Contributor
  15. roryabraham commented on Mar 5, 2024

    @roryabraham
    Contributor

    typo, it's +rb2 not +rbt

  16. roryabraham commented on Mar 5, 2024

    @roryabraham
    Contributor

    found logs, looks like an Idology error

  17. roryabraham commented on Mar 5, 2024

    @roryabraham
    Contributor

    Using mock Idology ExpectID API response

    (throws error response)

    lol

  18. roryabraham commented on Mar 5, 2024

    @roryabraham
    Contributor

    this is a fun gotcha. The Idology ExpectID mock is set up to fail if the last name of the user matches the middle name (just because we needed a way to test failure scenarios in the mock).

    In this case, you used Bobbeth for the last name on this request, which caused that to fail.

    So all this is expected behavior.

  19. removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded 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