Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[HOLD for payment 2021-11-04] VBA - User can proceed to next steps when entering 0's to the fields without any error message #5705

Closed
kavimuru opened this issue Oct 6, 2021 · 17 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Engineering External Added to denote the issue can be worked on by a contributor Weekly KSv2

Comments

@kavimuru
Copy link

kavimuru commented Oct 6, 2021

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Bug found when executing #5531

Action Performed:

  1. Launch the app
  2. Log in with expensifail account
  3. Enable the Staging Server
  4. Click on deeplink
  5. Select Chase
  6. Put Log in and Password
  7. Select Saving
  8. Start put all Information for VBA flow
  9. Enter invalid values for zip Code, TaxID Number and phone Number
  10. In Personal Information put invalid values for SSN

Expected Result:

Error message is displayed for the fields with invalid values

Actual Result:

Able to procced with flow without any error message using 0's as value for fields

Workaround:

Unknown

Platform:

Where is this issue occurring?

  • Web
  • iOS
  • Android
  • Desktop App
  • Mobile Web

Version Number: 1.1.6-0

Reproducible in staging?: Yes
Reproducible in production?: Credentials doesn't work for production

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos:

Bug5268769_Screen_Recording_20211006-164441_New_Expensify.mp4
Bug5268769_Screen_Recording_20211006-164109_New_Expensify.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause.
Slack conversation:

View all open jobs on GitHub

@kavimuru kavimuru added the DeployBlockerCash This issue or pull request should block deployment label Oct 6, 2021
@OSBotify
Copy link
Contributor

OSBotify commented Oct 6, 2021

👋 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.

@MelvinBot
Copy link

Triggered auto assignment to @cead22 (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

@isagoico isagoico mentioned this issue Oct 7, 2021
5 tasks
@isagoico isagoico added Daily KSv2 and removed DeployBlockerCash This issue or pull request should block deployment Hourly KSv2 labels Oct 7, 2021
@akshayasalvi
Copy link
Contributor

akshayasalvi commented Oct 7, 2021

Proposal

I am guessing the valid range for SSN is 0001 to 9999. In the ValidationUtils, we have a function to check valid SSN.

function isValidSSNLastFour(ssnLast4) {
    return CONST.REGEX.SSN_LAST_FOUR.test(ssnLast4) && ssnLast4 !== '0000';
}

What are the invalid values for Tax IDs? and for Zipcode also is it 00001 as the smallest value? Will accordingly handle for TaxId and Zipcode.

@cead22 cead22 removed their assignment Oct 7, 2021
@cead22 cead22 added the External Added to denote the issue can be worked on by a contributor label Oct 7, 2021
@MelvinBot
Copy link

Triggered auto assignment to @Christinadobrzyn (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

@Christinadobrzyn
Copy link
Contributor

I'm ooo so unassigning myself/adding a new teammate!

@Christinadobrzyn Christinadobrzyn removed their assignment Oct 11, 2021
@Christinadobrzyn Christinadobrzyn added External Added to denote the issue can be worked on by a contributor and removed External Added to denote the issue can be worked on by a contributor labels Oct 11, 2021
@MelvinBot
Copy link

Triggered auto assignment to @puneetlath (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

@mvtglobally
Copy link

Issue reproducible during KI retests.

@MelvinBot MelvinBot added Weekly KSv2 Help Wanted Apply this label when an issue is open to proposals by contributors and removed Daily KSv2 Overdue labels Oct 13, 2021
@puneetlath
Copy link
Contributor

Job post is here: https://www.upwork.com/jobs/~01bab34e1f30eef399

@akshayasalvi is there a simple way to udpate the SSN_LAST_FOUR regex to account for this? If not, your solution seems good.

@akshayasalvi
Copy link
Contributor

@puneetlath Afaik certain look ahead operations and logics are not possible with javascript regex. If awarded, I'll try to otherwise implement the one I suggested. Does that work?

Can you also help me with the valid/invalid values for Tax Id Number? I'll get that fixed too in this one.

@parasharrajat
Copy link
Member

parasharrajat commented Oct 14, 2021

Proposal

  1. As per the rule, the last four digits of SSN can not be 0000. We have to update the regex for matching the SSN's last digits SSN_LAST_FOUR. It will skip 0000 .
^(?!0000)[0-9]{4}$
  1. Other parts are all set, We are already validating the SSN
    const errors = validateIdentity({
    .

It is supported in all browsers and other platforms.

@parasharrajat
Copy link
Member

@puneetlath Gentle Bump. I think this is part of N6. Thanks.

@puneetlath
Copy link
Contributor

Let's go with @parasharrajat's solution. I prefer the method of just updating the regex.

@MelvinBot MelvinBot removed the Help Wanted Apply this label when an issue is open to proposals by contributors label Oct 15, 2021
@mvtglobally
Copy link

Issue reproducible during KI retests.

@puneetlath
Copy link
Contributor

Not overdue. Waiting for production deploy.

@MelvinBot MelvinBot removed the Overdue label Oct 26, 2021
@mvtglobally
Copy link

Issue reproducible during KI retests.

@mountiny mountiny changed the title VBA - User can proceed to next steps when entering 0's to the fields without any error message [HOLD for payment 2021-11-04] VBA - User can proceed to next steps when entering 0's to the fields without any error message Oct 30, 2021
@mountiny mountiny added the Awaiting Payment Auto-added when associated PR is deployed to production label Oct 30, 2021
@mvtglobally
Copy link

Issue reproducible during KI retests

@puneetlath
Copy link
Contributor

Paid!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Engineering External Added to denote the issue can be worked on by a contributor Weekly KSv2
Projects
None yet
Development

No branches or pull requests