Skip to content

[Due for payment 2026-01-14] [$250] IOU - Infinite loading when delete IOU while other user hold the expense #76411

Closed

Description

@lanitochka17

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.66-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): gocemate+b2155693@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. User A submits expense to User B
  2. User B open the expense details page> More> Hold
  3. User A deletes the expense

Expected Result:

Empty chat should be displayed/ Expense should be deleted

Actual Result:

There is a infinite loading when submitter delete the expense while receiver is on hold page

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

On which of our officially supported platforms was this issue tested:

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

Screenshots/Videos

+++ Add any screenshot/video evidence

+++

Bug7017511_1764587785581.Recording__72.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
Issue Owner

Current Issue Owner: @JmillsExpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Dec 1, 2025
  2. melvin-bot commented on Dec 1, 2025

    @melvin-bot

    Triggered auto assignment to @JmillsExpensify (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. truph01 commented on Dec 2, 2025

    @truph01
    Contributor

    Proposal

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

    • There is an infinite loading state when the submitter deletes an expense while the receiver is viewing the hold screen for that expense.

    What is the root cause of that problem?

    • Although there is existing logic to navigate the user to the parent report upon expense deletion, this navigation is skipped due to an early return in
      if ((!isFocused && !isReportDetailOpenInRHP) || isInNarrowPaneModal) {

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

    • We should allow navigation to the parent report even when the hold screen is currently displayed. The logic that determines whether navigation should occur needs to be updated to include the hold screen (and potentially other screens, which can be evaluated later).
                const isHoldScreenOpenInRHP = [SCREENS.MONEY_REQUEST.HOLD].find((r) => r === currentRoute?.name);
                if ((!isFocused && !isReportDetailOpenInRHP && !isHoldScreenOpenInRHP) || isInNarrowPaneModal) {
                    return;
                }
    

    or

                const isHoldScreenOpenInRHP = [SCREENS.MONEY_REQUEST.HOLD].find((r) => r === currentRoute?.name) && reportTransactionIDs.includes(currentRoute?.params?.transactionID);
                if ((!isFocused && !isReportDetailOpenInRHP && !isHoldScreenOpenInRHP) || isInNarrowPaneModal) {
                    return;
                }
    

    What alternative solutions did you explore? (Optional)

  4. melvin-bot commented on Dec 5, 2025

    @melvin-bot

    @JmillsExpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

  5. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Dec 9, 2025
  6. changed the title [-]IOU - Infinite loading when delete IOU while other user hold the expense[/-] [+][$250] IOU - Infinite loading when delete IOU while other user hold the expense[/+] on Dec 9, 2025
  7. melvin-bot commented on Dec 9, 2025

    @melvin-bot
  8. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Dec 9, 2025
  9. melvin-bot commented on Dec 9, 2025

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @alitoshmatov (External)

  10. JmillsExpensify commented on Dec 9, 2025

    @JmillsExpensify
    Contributor

    Bug report looks good so opening up for proposals

  11. 57 remaining items

  12. melvin-bot commented on Feb 16, 2026

    @melvin-bot

    @JmillsExpensify Huh... This is 4 days overdue. Who can take care of this?

  13. melvin-bot commented on Feb 20, 2026

    @melvin-bot

    @JmillsExpensify 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

  14. truph01 commented on Feb 21, 2026

    @truph01
    Contributor

    @JmillsExpensify I have not received payment yet.

  15. JmillsExpensify commented on Feb 21, 2026

    @JmillsExpensify
    Contributor

    Just sent you an offer.

  16. JmillsExpensify commented on Feb 27, 2026

    @JmillsExpensify
    Contributor

    @truph01 still waiting for you to accept the offer

  17. truph01 commented on Mar 2, 2026

    @truph01
    Contributor

    @JmillsExpensify I've accepted the offer!

  18. JmillsExpensify commented on Mar 2, 2026

    @JmillsExpensify
    Contributor

    Thanks. All paid out.

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 productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions