-
Notifications
You must be signed in to change notification settings - Fork 3.8k
fix: KYC flow doesn't trigger after adding bank account when paying another user #92154
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
Open
samranahm
wants to merge
4
commits into
Expensify:main
Choose a base branch
from
samranahm:91873/trigger-kyc-after-adding-account
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+64
−4
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
b56c7d7
update clearPersonalBankAccount function to optionally preserve routi…
samranahm d1e59aa
update clearPersonalBankAccount call to ensure routing data is preserved
samranahm 2d2226a
Rename parameter and add JSDoc comment
samranahm 95637e3
Add tests for clearPersonalBankAccount function
samranahm File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When this entry point is reached from a normal wallet add-bank-account action after the user previously abandoned a payment/KYC-driven add-bank flow,
openPersonalBankAccountSetupView({})does not clearPERSONAL_BANK_ACCOUNT, and this call now preserves the oldonSuccessFallbackRoute/exitReportID. After the later wallet-initiated bank account succeeds,AddPersonalBankAccountPage.exitFlow(true)can continue the stale KYC/payment flow or dismiss to an old report instead of returning to the wallet. Preserve only routing data that was intentionally seeded for the current flow, or clear stale routing before this generic entry point is reused.Useful? React with 👍 / 👎.