-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[Due for payment 2025-05-22] [$250] Bank account - RHP back button on Business info does not return to Bank info confirmation page #60519
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
Comments
Triggered auto assignment to @OfstadC ( |
Triggered auto assignment to @marcaaron ( |
💬 A slack conversation has been started in #expensify-open-source |
👋 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:
|
Not a blocker. GR is under beta. @mitarachim Can you confirm you can connect EUR bank account with brand new account? |
Hello @hungvu193 , i end up in Screen.Recording.2025-04-19.at.8.53.39.AM.mp4 |
Oh looks like your account is under beta. |
ProposalPlease re-state the problem that we are trying to solve in this issue.Bank account - RHP back button on Business info does not return to Bank info confirmation page What is the root cause of that problem?When we connect to bank using NON-USD currency, we have some few steps screens and each screen will have some substeps which is:
When we complete each screen for example in this case BankInfo, we will get redirected to BusinessInfo and when we press the go back button we will redirect back the user to BankInfo App/src/pages/ReimbursementAccount/NonUSD/NonUSDVerifiedBankAccountFlow.tsx Lines 63 to 65 in 8ed9c09
But why after we press the back button in BusinessInfo step we got redirected to BankInfo into the first substep screen?, actually we already have a logic right here to handle this cases which we will show the substep screen to the user based on the provided data information by the user earlier App/src/pages/ReimbursementAccount/NonUSD/BankInfo/BankInfo.tsx Lines 43 to 45 in 8ed9c09
App/src/pages/ReimbursementAccount/NonUSD/BankInfo/BankInfo.tsx Lines 77 to 85 in 8ed9c09
But the
But in this case why we fail to calculate to correct index of substep screens?, as I said the startFrom is depends on corpayFields value which is only retrieved from BE and we also pass initWithStoredValues: false to the useOnyx function
So App/src/pages/ReimbursementAccount/NonUSD/utils/getInitialSubStepForBankInfoStep.ts Lines 15 to 17 in 8ed9c09
What changes do you think we should make in order to solve the problem?This changes was introduced in this PR #58371, I think maybe there's some issues because corpayFields like very stricts meaning if we change the country or currency, we need to re-call the To resolve this issue we can remove this option from the useOnyx method Alternatively instead of using useOnyx here for the
App/src/pages/ReimbursementAccount/NonUSD/BankInfo/BankInfo.tsx Lines 43 to 45 in 8ed9c09
We can use Onyx.connect inside getInputKeysForBankInfoStep for the corpayFields value
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?N/A What alternative solutions did you explore? (Optional) |
Also cc @burczu |
Coming from the perspective of the Web Deploy, I removed the |
I am Michał from Callstack - expert contributor group. I’d like to work on this job. Im also one of the authors of this whole flow this is now behind beta so I have all the needed context. |
Sounds good! |
Because there were other issues with the flow and they're all relatively small we've decided to fix all of them in one big follow-up issue - #60633 |
Draft PR for this and other related issues is up. However I haven't added solution for this particular issue yet |
Sounds good. Link us the PR here if you can 🙇 |
Here it is. I'll be working on fixing this particular issue today :) |
@rushatgabhane 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
PR that fixes it just got merged. This will be ready to be retested soon. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.45-21 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 2025-05-22. 🎊 For reference, here are some details about the assignees on this issue:
|
@rushatgabhane @OfstadC @rushatgabhane The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.1.30-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No, reproducible on hybrid only
If this was caught during regression testing, add the test name, ID and link from TestRail: #56931
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Workspace Settings
Action Performed:
Precondition:
Expected Result:
In Step 10, RHP back button on the first substep of Business info step will return to the previous page which is Bank info confirmation page.
Actual Result:
In Step 10, RHP back button on the first substep of Business info step returns to the first substep of Bank info section instead of the previous page which is Bank info confirmation page.
This is inconsistent with Step 15 where RHP back button on Owner info page returns to Business info confirmation page.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6806819_1745019095938.20250419_072005.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @OfstadCThe text was updated successfully, but these errors were encountered: