Skip to content

Expense - Amount field and green button shows "Scanning" instead of expense amount #82277

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.3.18-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: #81156
Email or phone of affected tester (no customers): sjoijsnonisnjidosd@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to self DM.
  3. Go offline.
  4. Create a scan expense.
  5. Click Submit it to someone.
  6. Select workspace chat.
  7. On confirm page, click Amount.
  8. Enter amount and save it.
    BUG 1: Amount field still shows "Scanning...".
    BUG 2: Green button changes to "Create Scanning... expense".
  9. Click Merchant.
  10. Enter merchant and save it.
    → Amount field changes to the entered amount. Green button shows "Create RM10.00 expense". (Expected).

Expected Result:

In Step 8, after entering amount, Amount field will show the entered amount. Green button will show "Create $x expense".

Actual Result:

In Step 8, Amount field still shows "Scanning...". Green button changes to "Create Scanning... expense".

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7075968_1770911028296.8.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 Feb 12, 2026
  2. melvin-bot commented on Feb 12, 2026

    @melvin-bot

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

  3. melvin-bot commented on Feb 12, 2026

    @melvin-bot

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

  4. melvin-bot commented on Feb 12, 2026

    @melvin-bot

    Triggered auto assignment to @NicMendonca (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 Feb 12, 2026

    @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. brunovjk commented on Feb 12, 2026

    @brunovjk
    Contributor

    @nkdengineer can you help us solve this regression? Thank you.

  7. nkdengineer commented on Feb 12, 2026

    @nkdengineer
    Contributor

    Let revert the PR first, I will revisit tomorrow.

  8. removed
    DeployBlockerIndicates it should block deploying the API
    on Feb 12, 2026
  9. IuliiaHerets commented on Feb 13, 2026

    @IuliiaHerets

    Issue is not repro anymore, Chrome / v9.3.18-6

    Screen.Recording.2026-02-13.at.14.24.49.mp4
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.EngineeringHourlyKSv2ReviewingHas a PR in review

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions