Skip to content

[Due for payment 2026-03-06] [BT-004] Create DynamicVerifyAccountPage Component #80909

Closed

Description

@mjasikowski

Description

Current State:

  • Multiple VerifyAccountPage components exist for different contexts
  • Each has hardcoded backTo logic based on the flow it serves
  • The base component logic is in VerifyAccountPageBase.tsx
  • Example existing implementations:
    • pages/settings/Wallet/VerifyAccountPage/index.tsx
    • pages/settings/Security/TwoFactorAuth/VerifyAccountPage.tsx

Expected State:

  • Create a single DynamicVerifyAccountPage component
  • Component reuses VerifyAccountPageBase for core functionality
  • Implements dynamic back logic using getPathWithoutSuffix()
  • Implements forward logic (static destination or via FORWARD_TO_MAPPINGS)
  • No backTo parameter in URL - context comes from the path itself

Implementation:

Create App/src/pages/settings/DynamicVerifyAccountPage.tsx:

import React from 'react';
import Navigation from '@libs/Navigation/Navigation';
import DYNAMIC_ROUTES from '@src/ROUTES';
import VerifyAccountPageBase from './VerifyAccountPageBase';

function getPathWithoutSuffix(dynamicSuffix: string): string {
    const path = Navigation.getActiveRoute();
    return path ? path.replace(`/${dynamicSuffix}`, '') : ROUTES.HOME;
}

function DynamicVerifyAccountPage() {
    const handleGoBack = () => {
        const backRoute = getPathWithoutSuffix(DYNAMIC_ROUTES.VERIFY_ACCOUNT.path);
        Navigation.goBack(backRoute);
    };

    return (
        <VerifyAccountPageBase
            onGoBack={handleGoBack}
            onGoForward={handleGoForward}
        />
    );
}

export default DynamicVerifyAccountPage;

Scope

Files:

  • App/src/pages/settings/DynamicVerifyAccountPage.tsx (new file)
  • May need to modify VerifyAccountPageBase.tsx if it doesn't accept callback props

Dependencies:

Activity

  1. added
    InternalRequires API changes or must be handled by Expensify staff
    on Jan 29, 2026
  2. mjasikowski commented on Feb 11, 2026

    @mjasikowski
    ContributorAuthor

    This was reverted as some bugs have surfaced after merging

  3. added
    ReviewingHas a PR in review
    and removed on Feb 12, 2026
  4. 2 remaining items

  5. huult commented on Feb 13, 2026

    @huult
    Contributor

    No, I don’t think so, because #81392 (comment) was reverted.

  6. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Feb 13, 2026
  7. changed the title [-][BT-004] Create DynamicVerifyAccountPage Component[/-] [+][Due for payment 2026-02-20] [BT-004] Create DynamicVerifyAccountPage Component[/+] on Feb 13, 2026
  8. melvin-bot commented on Feb 13, 2026

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  9. melvin-bot commented on Feb 13, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.18-8 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 2026-02-20. 🎊

    For reference, here are some details about the assignees on this issue:

    • @huult requires payment through NewDot Manual Requests
    • @collectioneur does not require payment (Contractor)
  10. changed the title [-][Due for payment 2026-02-20] [BT-004] Create DynamicVerifyAccountPage Component[/-] [+][BT-004] Create DynamicVerifyAccountPage Component[/+] on Feb 20, 2026
  11. mjasikowski commented on Feb 20, 2026

    @mjasikowski
    ContributorAuthor

    No payment needed - fixed price project

  12. changed the title [-][BT-004] Create DynamicVerifyAccountPage Component[/-] [+][Due for payment 2026-03-06] [BT-004] Create DynamicVerifyAccountPage Component[/+] on Feb 27, 2026
  13. melvin-bot commented on Feb 27, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.26-8 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 2026-03-06. 🎊

    For reference, here are some details about the assignees on this issue:

    • @huult requires payment through NewDot Manual Requests
    • @collectioneur does not require payment (Contractor)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionInternalRequires API changes or must be handled by Expensify staffWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions