App
App copied to clipboard
Expensify
With new account, while connecting bank account, it still at the second step after the first press.
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
- Create new account, after that create new workspace.
- Go to connect bank account => Connect bank account manually => Enter valid information for the first step => Press Save.
- Go press back arrow to go the main Connect Bank Account => Connect with Plaid => Enter all valid information => Choose Plaid Bank Account => Press Save.
- Continue to enter the routing number then press Continue => Enter valid information for step 2 => Press Save & Continue.
- Notice that it stays at Step 2 for the first press even there's no error message. In some cases, it stuck at the second step until you reload the page.
Expected Result
User can connect bank account without any issue.
Actual Result
User still stays at the bank account second step after the first press without any error message.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
- [ ] Android / native
- [ ] Android / Chrome
- [ ] iOS / native
- [ ] iOS / Safari
- [x] MacOS / Chrome / Safari
- [ ] MacOS / Desktop
Version Number: v1.2.98-2 Reproducible in staging?: needs reproduction Reproducible in production?: needs reproduction 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
https://user-images.githubusercontent.com/43996225/231242726-739e2d38-87c2-4587-87c0-5f1cdd397e96.mov
Expensify/Expensify Issue URL: Issue reported by: @hungvu193 Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1681185649601179
Triggered auto assignment to @adelekennedy (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.
Bug0 Triage Checklist (Main S/O)
- [ ] This "bug" occurs on a supported platform (ensure
Platformsin 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
@kavimuru did you add the needs reproduction label because you weren't able to reproduce the issue?
@adelekennedy this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
@adelekennedy 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
hmm - I can't reproduce this either but @hungvu193 can, @kavimuru will you try to reproduce once more?
@adelekennedy this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks!
@adelekennedy this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks!