Skip to content

Expense - Zero amounts can be created for P2P requests #76851

Closed

Description

@vincdargento

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: v9.2.73-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #75542
Email or phone of affected tester (no customers): applausetester+ds@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: Mac 14.5/ Chrome
App Component: Money Requests

Action Performed:

  1. Navigate to https://staging.new.expensify.com/
  2. Login with a beta account that has a workspace
  3. Click on FAB > Create Expense > Enter 0.00 on Amount > Next
  4. Click on the to Field and Change the selected workspace to any user to create a p2p expense
  5. Click on Create Expense

Expected Result:

Violation is shown before the expense is created.

Actual Result:

Unexpected Error is shown after the expense is created

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

bug.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @Gonals

Activity

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

    @melvin-bot

    Triggered auto assignment to @lydiabarclay (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 Dec 5, 2025

    @melvin-bot

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

  4. melvin-bot commented on Dec 5, 2025

    @melvin-bot

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

  5. github-actions commented on Dec 5, 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. lydiabarclay commented on Dec 6, 2025

    @lydiabarclay
    Contributor
  7. removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Dec 8, 2025
  8. self-assigned this
    on Dec 8, 2025
  9. Gonals commented on Dec 8, 2025

    @Gonals
    Contributor

    Assigning to self. No need to block, as it is behind a beta

  10. lydiabarclay commented on Dec 11, 2025

    @lydiabarclay
    Contributor

    @Gonals I keep trying to make you the primary assignee and GH keeps reverting it, not sure why

  11. mjasikowski commented on Dec 12, 2025

    @mjasikowski
    Contributor

    @lydiabarclay maybe your K2 extension is out of date? Anyway, I sorted that out for you

  12. Gonals commented on Dec 12, 2025

    @Gonals
    Contributor

    PR was reverted, so closing

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.DailyKSv2EngineeringImprovementItem broken or needs improvement.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions