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 2023-09-21] Bank account - Temporarily disabled message not displayed after 21 attempts #26354

Closed
2 of 6 tasks
lanitochka17 opened this issue Aug 30, 2023 · 16 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Improvement Item broken or needs improvement.

Comments

@lanitochka17
Copy link

lanitochka17 commented Aug 30, 2023

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


Issue found when executing PR #20747

Action Performed:

  1. From NewDot, try adding a deposit account. Choose any Plaid bank, and enter 19 times some wrong credentials
  2. Exit Plaid's modal. You should be able to choose a Plaid bank again. Enter 2 more wrong credentials
  3. Exit Plaid's modal and try adding deposit account again

Expected Result:

User should not be able to use Plaid again

Actual Result:

Able to use plaid login again

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

Version Number: 1.3.59-4

Reproducible in staging?: Yes

Reproducible in production?: No

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

Notes/Photos/Videos: Any additional supporting documentation

Bug6183235_screen-20230830-161947.1.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

@lanitochka17 lanitochka17 added the DeployBlockerCash This issue or pull request should block deployment label Aug 30, 2023
@OSBotify
Copy link
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.

@melvin-bot
Copy link

melvin-bot bot commented Aug 30, 2023

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

@luacmartins
Copy link
Contributor

FWIW I can also keep entering invalid credentials in prod, so I don't think this is a blocker

@luacmartins
Copy link
Contributor

I'm gonna demote this to NAB since I could reproduce the behavior in prod. @nkuoch can you take a look at this one when you get a chance?

@luacmartins luacmartins removed the DeployBlockerCash This issue or pull request should block deployment label Aug 31, 2023
@marcaaron marcaaron added Daily KSv2 and removed Hourly KSv2 labels Aug 31, 2023
@marcaaron marcaaron removed their assignment Aug 31, 2023
@marcaaron marcaaron added Bug Something is broken. Auto assigns a BugZero manager. and removed Engineering labels Aug 31, 2023
@melvin-bot
Copy link

melvin-bot bot commented Aug 31, 2023

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

@melvin-bot
Copy link

melvin-bot bot commented Aug 31, 2023

Bug0 Triage Checklist (Main S/O)

  • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
  • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
    • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
  • This bug is reproducible using the reproduction steps in the OP. S/O
    • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
    • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
  • This issue is filled out as thoroughly and clearly as possible
    • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
  • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

@nkuoch nkuoch self-assigned this Aug 31, 2023
@nkuoch
Copy link
Contributor

nkuoch commented Aug 31, 2023

@lanitochka17 can you tell me which email you tested it from in the video?

@lanitochka17
Copy link
Author

lanitochka17 commented Aug 31, 2023

@nkuoch nkuoch added Weekly KSv2 Improvement Item broken or needs improvement. and removed Daily KSv2 labels Aug 31, 2023
@nkuoch
Copy link
Contributor

nkuoch commented Aug 31, 2023

PR in progress #26394

@nkuoch nkuoch added the Reviewing Has a PR in review label Sep 1, 2023
@melvin-bot melvin-bot bot added Weekly KSv2 and removed Weekly KSv2 labels Sep 1, 2023
@alexpensify
Copy link
Contributor

PR is still in review

@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels Sep 14, 2023
@melvin-bot melvin-bot bot changed the title Bank account - Temporarily disabled message not displayed after 21 attempts [HOLD for payment 2023-09-21] Bank account - Temporarily disabled message not displayed after 21 attempts Sep 14, 2023
@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Sep 14, 2023
@melvin-bot
Copy link

melvin-bot bot commented Sep 14, 2023

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

@melvin-bot
Copy link

melvin-bot bot commented Sep 14, 2023

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.69-2 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 2023-09-21. 🎊

After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

  • External issue reporter
  • Contributor that fixed the issue
  • Contributor+ that helped on the issue and/or PR

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

  • Merged PR within 3 business days of assignment - 50% bonus
  • Merged PR more than 9 business days after assignment - 50% penalty

@melvin-bot
Copy link

melvin-bot bot commented Sep 14, 2023

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:

  • [@nkuoch] The PR that introduced the bug has been identified. Link to the PR:
    Not a bug, more of a feature - we just never implemented it before
  • [@nkuoch] 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:
    N/A - Same as above
  • [@nkuoch] 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:
    N/A - Same as above
  • [@nkuoch] Determine if we should create a regression test for this bug.
    No, not important enough to create one - especially as it's just something we created to prevent some users from overusing plaid in some situations, but not for all.
  • [@nkuoch] 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.
    N/A
  • [@alexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon: N/A

@nkuoch nkuoch closed this as completed Sep 14, 2023
@nkuoch nkuoch reopened this Sep 14, 2023
@alexpensify
Copy link
Contributor

@nkuoch - correct me if I'm wrong, but I don't think there's a payment here in Upwork.

Here is the payment summary:

  • External issue reporter - Applause - Payment N/A
  • Contributor that fixed the issue - Internal - Payment N/A
  • Contributor+ that helped on the issue and/or PR - @ArekChr Payment via vendor

Upwork Job: N/A

*If applicable, the bonuses will be applied on the final payment

Extra Notes regarding payment:

@melvin-bot melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels Sep 21, 2023
@nkuoch
Copy link
Contributor

nkuoch commented Sep 21, 2023

ah yes sorry.

@alexpensify
Copy link
Contributor

All good, I'm going to close this GH since there is no payment action here.

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 Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Improvement Item broken or needs improvement.
Projects
None yet
Development

No branches or pull requests

6 participants