Skip to content

[Payments Buttons] Reports - Pay with business account option is missing in Pay menu after reset app #71285

Closed

Description

@jponikarchuk

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Version Number: 9.2.18-1
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from TestRail: #70106
Email or phone of affected tester (no customers): applausetester+250902kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Search

Action Performed:

Precondition:

  • Workspace is set up with bank account.
  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create an expense.
  4. Click Submit and Approve.
  5. Go to Account > Troubleshoot > Reset and refresh > Clear cache and restart.
  6. Go to Reports > Reports.
  7. Select the report via checkbox.
  8. Click dropdown button > Pay.
    BUG: Pay with business account option is missing.
  9. Open the report.
  10. Click app back button.
  11. Click dropdown button > Pay.
  12. Pay with business account option is only displayed after opening the expense report.

Expected Result:

In Step 8, after reset app, Pay with business account option will be present in Pay menu.

Actual Result:

In Step 8, after reset app, Pay with business account option is missing in Pay menu.
In Step 12, only after opening the expense report, Pay menu shows Pay with business account option.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 25, 2025
  2. melvin-bot commented on Sep 25, 2025

    @melvin-bot

    Triggered auto assignment to @joekaufmanexpensify (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.

  3. melvin-bot commented on Sep 25, 2025

    @melvin-bot

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

  4. melvin-bot commented on Sep 25, 2025

    @melvin-bot

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

  5. github-actions commented on Sep 25, 2025

    @github-actions
    Contributor

    👋 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.
  6. hungvu193 commented on Sep 25, 2025

    @hungvu193
    Contributor

    Checking ...

  7. hungvu193 commented on Sep 25, 2025

    @hungvu193
    Contributor

    After resetting, the data of this report (not the transaction) can only be accessed via snapshot. That's why isExpenseReport here returns false and bank account option doesn't appear:

    const isExpenseReport = isExpenseReportUtil(selectedReportID);

    Image

    I tried to get the report via useOnyx get it from snapshot, however if I used it inside useBulkPayOptions, isOnSearch is false and hash is undefined, so it doesn't use data from snapshot 😭 . Still finding the solution.....

    Image
  8. 10 remaining items

  9. grgia commented on Sep 26, 2025

    @grgia
    Contributor

    @madmax330 taking this over

  10. grgia commented on Sep 29, 2025

    @grgia
    Contributor

    Adding Reviewing label

  11. melvin-bot commented on Oct 15, 2025

    @melvin-bot

    @hungvu193, @grgia 10 days overdue. Is anyone even seeing these? Hello?

  12. melvin-bot commented on Oct 17, 2025

    @melvin-bot

    @hungvu193, @grgia 12 days overdue now... This issue's end is nigh!

  13. melvin-bot commented on Oct 20, 2025

    @melvin-bot

    This issue has not been updated in over 14 days. @hungvu193, @grgia eroding to Weekly issue.

  14. melvin-bot commented on Nov 12, 2025

    @melvin-bot

    This issue has not been updated in over 15 days. @hungvu193, @grgia eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  15. hungvu193 commented on Nov 17, 2025

    @hungvu193
    Contributor

    Good to close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringMonthlyKSv2ReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions