Skip to content

[Due for payment 2025-10-21] Expense - "Select at least one expense" error is not shown when there is no result #72310

Closed

Description

@mitarachim

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

Action Performed:

Precondition:

  • Have at least 16 unreported expenses in self DM.
  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create an empty report in workspace chat.
  4. Click Add expense > Add unreported expense.
  5. Enter anything that will not return any result.
  6. Click Add to report.

Expected Result:

"Select at least one expense" error will be shown when there is no result

Actual Result:

"Select at least one expense" error is not shown when there is no result

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

Bug6970652_1760095838228.Screen_Recording_2025-10-10_at_19.27.42.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @zanyrenney

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Oct 10, 2025
  2. melvin-bot commented on Oct 10, 2025

    @melvin-bot

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

  3. melvin-bot commented on Oct 10, 2025

    @melvin-bot

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

  4. melvin-bot commented on Oct 10, 2025

    @melvin-bot

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

  5. github-actions commented on Oct 10, 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. 7 remaining items

  7. brunovjk commented on Oct 13, 2025

    @brunovjk
    Contributor

    Yes, I tested and this issue is fixed here, I'm waiting for the QA team to confirm it too 🤞

  8. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Oct 14, 2025
  9. changed the title [-]Expense - "Select at least one expense" error is not shown when there is no result[/-] [+][Due for payment 2025-10-21] Expense - "Select at least one expense" error is not shown when there is no result[/+] on Oct 14, 2025
  10. melvin-bot commented on Oct 14, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.30-6 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 2025-10-21. 🎊

  11. melvin-bot commented on Oct 14, 2025

    @melvin-bot

    @Valforte @zanyrenney The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  12. zanyrenney commented on Oct 22, 2025

    @zanyrenney
    Contributor

    hey @Valforte can you confirm the contributors here please?

  13. brunovjk commented on Oct 22, 2025

    @brunovjk
    Contributor

    No payment will be necessary here @zanyrenney, this issue was a regression that has already been fixed. Payment will be processed in the original issue. Thank you.

  14. zanyrenney commented on Oct 23, 2025

    @zanyrenney
    Contributor

    Thanks @brunovjk !

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions