Skip to content

Expense - Converted amount shows negative amount and with USD currency #78522

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.88-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: #78233
Email or phone of affected tester (no customers): sidojnosidjosijd@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Personal and group policy's default currency is not USD.
  1. Go to staging.new.expensify.com
  2. Go to self DM.
  3. Create an expense with any currency other than USD.
  4. Open the expense report.

Expected Result:

Converted amount will not show negative amount and with correct default currency.

Actual Result:

Converted amount shows negative amount and with USD currency.
The amount is also not converted.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7038574_1767012114196.3.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.
    DeployBlockerIndicates it should block deploying the API
    on Dec 29, 2025
  2. melvin-bot commented on Dec 29, 2025

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #78233

  3. melvin-bot commented on Dec 29, 2025

    @melvin-bot

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

  4. melvin-bot commented on Dec 29, 2025

    @melvin-bot

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

  5. github-actions commented on Dec 29, 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. removed
    DeployBlockerIndicates it should block deploying the API
    on Dec 29, 2025
  7. mollfpr commented on Dec 29, 2025

    @mollfpr
    Contributor

    @youssef-lr Could you take a look at this? Maybe we can fix it so we don't have to revert the PR.

    cc @hoangzinh

  8. youssef-lr commented on Dec 29, 2025

    @youssef-lr
    Contributor

    yes on it

  9. youssef-lr commented on Dec 29, 2025

    @youssef-lr
    Contributor

    @mollfpr this is not coming from my PR, I reverted locally and can still reproduce.

  10. mollfpr commented on Dec 30, 2025

    @mollfpr
    Contributor

    We have reverted #78471, and I can't repro the issue. Closing!

  11. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Dec 30, 2025
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.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions