Wallet - mweb - Continue CTA not visible in bank account success page

[mitarachim]

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.7-1
Reproducible in staging?: Yes
Reproducible in production?: Unable to check
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5666568
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: iPhone 16/iOS 18/Safari 18
App Component: User Settings

Action Performed:

Scenario 1:

1. Navigate to staging.new.expensify.com on mobile web
2. Go to Settings >> Wallet >> Add bank account
3. Complete the Plaid flow selecting Wells Fargo or Chase option
4. User navigated to add bank account page
5. Select either saving or checking account
6. Observe the Continue button not visible on add bank account success page

Expected Result:

Continue button should be visible at the bottom in add bank account success page

Actual Result:

Continue button not visible at all in add bank account success page

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

https://github.com/user-attachments/assets/6912f9a3-d0f5-4e23-8035-1b59d3571587

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @stephanieelliott (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Triggered auto assignment to @robertjchen (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 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.

[daledah]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Continue button not visible at all in add bank account success page

What is the root cause of that problem?

We're not wrapping Confirmation page here inside ScrollView:

App/src/pages/AddPersonalBankAccountPage.tsx

Lines 93 to 100 in 7bda731

	{shouldShowSuccess ? (
	<ConfirmationPage
	heading={translate('addPersonalBankAccountPage.successTitle')}
	description={translate('addPersonalBankAccountPage.successMessage')}
	shouldShowButton
	buttonText={translate('common.continue')}
	onButtonPress={() => exitFlow(true)}
	/>

What changes do you think we should make in order to solve the problem?

Wrap Confirmation page inside ScrollView:

App/src/pages/AddPersonalBankAccountPage.tsx

Lines 93 to 100 in 7bda731

	{shouldShowSuccess ? (
	<ConfirmationPage
	heading={translate('addPersonalBankAccountPage.successTitle')}
	description={translate('addPersonalBankAccountPage.successMessage')}
	shouldShowButton
	buttonText={translate('common.continue')}
	onButtonPress={() => exitFlow(true)}
	/>

{shouldShowSuccess ? (
        <ScrollView contentContainerStyle={styles.flexGrow1}>
            <ConfirmationPage
                heading={translate('addPersonalBankAccountPage.successTitle')}
                description={translate('addPersonalBankAccountPage.successMessage')}
                shouldShowButton
                buttonText={translate('common.continue')}
                containerStyle={styles.h100}
                onButtonPress={() => exitFlow(true)}
             />
</ScrollView>

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

None

What alternative solutions did you explore? (Optional)

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.