Repository navigation
Payments - User is taken to production flow for adding Personal bank account and VBA - Toggling staging server has no effect #10084
Description
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
- Go to staging.new.expensify.com and login
- Go to settings > preferences > toggle "use staging server"
- Click payments > Bank account
- Look for "Wells Fargo"
- Search for the "Wells Fargo" and initiate
Expected Result:
User should see "Wells Fargo" option and able to continue
Actual Result:
Bank name is not available in the list and searching and continuing triggers production flow
NOTE: Looks like toggling staging server is not effective. (We are blocked with all the regression test case which require adding VBA)
Workaround:
Unknwon
Platform:
Where is this issue occurring?
- Web
- Android
- Desktop App
- Mobile Web
Version Number: 1.1.86-0
Reproducible in staging?: y
Reproducible in production?: n/a
Email or phone of affected tester (no customers): applausetester+0716mn@applause.expensifail.com / Utest123
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
Bug5662706_Recording__367.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Activity
melvin-bot commentedon Jul 25, 2022
Triggered auto assignment to @danieldoglas (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.danieldoglas commentedon Jul 26, 2022
I'm not fully sure we would hide something on staging servers. Will ask this in slack.
danieldoglas commentedon Jul 26, 2022
This is related to this PR: #9423
Since we moved plaid's logic from web-s to web-e, changing the flag to use staging on web-s won't do anything in this flow anymore.
I'm putting this into a discussion that's happening right now about using staging env for web-e.
luacmartins commentedon Jul 27, 2022
@danieldoglas So should this be tested in production now?
danieldoglas commentedon Jul 27, 2022
I don't think Applause will have credentials for testing in production. There's a discussion ongoing right now. I think we'll actually send builds from staging pointing to staging soon. https://expensify.slack.com/archives/C03TQ48KC/p1658415135702599
luacmartins commentedon Jul 27, 2022
Sounds good! So we are either fixing it by pointing our staging build to staging API or doing internal prodQA for these?
danieldoglas commentedon Aug 1, 2022
moving this to weekly since it's in discussion
melvin-bot commentedon Aug 10, 2022
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a production regression has occurred a Root Cause Analysis is required. Please follow the instructions here.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
melvin-bot commentedon Aug 10, 2022
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a production regression has occurred a Root Cause Analysis is required. Please follow the instructions here.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
iwiznia commentedon Aug 10, 2022
I think this will be solved by #10163 right?
danieldoglas commentedon Aug 15, 2022
it will! I'll close this and relate it on the other issue.
danieldoglas commentedon Oct 11, 2022