Skip to content

Expense - Confirm modal is not shown when there is an outstanding empty report #72835

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.33-0
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 BrowserStack: #71609
Email or phone of affected tester (no customers): jsodinjsdoijsiodsj@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create an expense.
  4. Click Submit on the expense preview.
  5. Open the expense report.
  6. Click Report.
  7. Click Remove from report.
  8. Go back to workspace chat.
  9. Click + > Create report.

Expected Result:

Confirm modal will be shown because there is already an outstanding empty report.

Actual Result:

Confirm modal is not shown when there is an outstanding empty report.

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 Oct 17, 2025
  2. melvin-bot commented on Oct 17, 2025

    @melvin-bot

    Triggered auto assignment to @abekkala (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. github-actions commented on Oct 17, 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.
  4. melvin-bot commented on Oct 17, 2025

    @melvin-bot

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

  5. melvin-bot commented on Oct 17, 2025

    @melvin-bot

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

  6. mountiny commented on Oct 17, 2025

    @mountiny
    Contributor
  7. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Oct 17, 2025
  8. blimpich commented on Oct 17, 2025

    @blimpich
    Contributor

    Update: CP failed due to new workflow restrictions

    Waiting for those things to resolve before we can finish CP, then re-test this.

  9. kavimuru commented on Oct 17, 2025

    @kavimuru

    Bug is still reproducible

    72835.mp4
  10. puneetlath commented on Oct 20, 2025

    @puneetlath
    Contributor

    The PR implementing this was reverted. That's why it's not being seen. Going to go ahead and close this.

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions