Skip to content

Dev : Duplicate Amount Screen Appears When Creating an Expense #70149

Closed

Description

@m-natarajan

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:
Reproducible in staging?: Needs Reproduction
Reproducible in production?: Needs Reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @aldo-expensify
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

  1. Create a report in a workspace chat
  2. Click more and add a new expense
  3. Enter the amount
  4. Tap Next or proceed to the next step
  5. Sometimes, instead of continuing, the app shows another amount screen

Expected Result:

After entering the amount once, the user should proceed to the next step without being prompted to enter the amount again.

Actual Result:

The app occasionally shows a second amount screen, requiring the user to re-enter the amount.

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop
Platforms Tested: On which of our officially supported platforms was this issue tested:
  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Screen.Recording.2025-09-08.at.3.25.14.PM.mov

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 8, 2025
  2. melvin-bot commented on Sep 8, 2025

    @melvin-bot

    Triggered auto assignment to @strepanier03 (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. truph01 commented on Sep 9, 2025

    @truph01
    Contributor

    Maybe it comes from #69773

  4. melvin-bot commented on Sep 12, 2025

    @melvin-bot

    @strepanier03 Whoops! This issue is 2 days overdue. Let's get this updated quick!

  5. strepanier03 commented on Sep 16, 2025

    @strepanier03
    Contributor

    I'm not able to reproduce this behavior. I know the OP says "sometimes" it happens but I can't get it to happen at all.

  6. added
    BugSomething is broken. Auto assigns a BugZero manager.
    retest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause
    and removed
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 16, 2025
  7. melvin-bot commented on Sep 16, 2025

    @melvin-bot

    Current assignee @strepanier03 is eligible for the Bug assigner, not assigning anyone new.

  8. MelvinBot commented on Sep 16, 2025

    @MelvinBot
    Contributor

    This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

  9. brunovjk commented on Sep 16, 2025

    @brunovjk
    Contributor

    We reverted the PR that introduced this bug

  10. melvin-bot commented on Sep 19, 2025

    @melvin-bot

    @strepanier03 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  11. strepanier03 commented on Sep 20, 2025

    @strepanier03
    Contributor

    Closing this per the comment above about the bug causing PR being reverted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Needs ReproductionReproducible steps neededretest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions