Skip to content

[Due for payment 2026-01-16] [$250] Web - Expense - Pressing Enter on no result page proceeds to next page instead of blocking it #78593

Closed

Description

@jponikarchuk

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.89-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #78004
Email or phone of affected tester (no customers): jsoidjnsdoijsdojso@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Click + > Create expense > Manual.
  4. Without entering amount, click Currency.
  5. Type anything that will not return result.
  6. Hit Enter.
  7. Click RHP back button.
    BUG 1: Error shows up on amount input page.
  8. Enter amount.
  9. Click Currency.
  10. Type anything that will not return result.
  11. Hit Enter.
  12. Click RHP back button.
    BUG 2: RHP opens confirm page instead of amount input page.

Expected Result:

BUG 1: No error will show up on amount input page.
BUG 2: RHP will return to amount input page.

Actual Result:

BUG 1: Error shows up on amount input page.
BUG 2: RHP opens confirm page instead of amount input page.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022006118654654184338
  • Upwork Job ID: 2006118654654184338
  • Last Price Increase: 2026-01-06
Issue OwnerCurrent Issue Owner: @stephanieelliott

Activity

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

    @melvin-bot

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

  3. melvin-bot commented on Dec 30, 2025

    @melvin-bot

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

  4. melvin-bot commented on Dec 30, 2025

    @melvin-bot

    Triggered auto assignment to @stephanieelliott (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 30, 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. tgolen commented on Dec 30, 2025

    @tgolen
    Contributor

    Checking in Slack to see if this is caused by #78004

  7. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Dec 30, 2025
  8. 34 remaining items

  9. melvin-bot commented on Jan 9, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.96-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 2026-01-16. 🎊

    For reference, here are some details about the assignees on this issue:

    • @akinwale requires payment through NewDot Manual Requests
    • @Eskalifer1 requires payment (Needs manual offer from BZ)
  10. melvin-bot commented on Jan 9, 2026

    @melvin-bot

    @akinwale @stephanieelliott 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]

  11. akinwale commented on Jan 13, 2026

    @akinwale
    Contributor

    BugZero Checklist:

    • [@akinwale] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment: N/A

    • [@akinwale] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: N/A

    • [@akinwale] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Test:

    1. Launch Expensify.
    2. Go to workspace chat.
    3. Click + > Create expense > Manual.
    4. Without entering amount, click Currency.
    5. Type any keyword that will not return result.
    6. Hit Enter.
    7. Click the RHP back button.
    8. Verify that no error message is displayed on the amount input page.

    Do we agree 👍 or 👎?

  12. melvin-bot commented on Jan 16, 2026

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@stephanieelliott)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/2006118654654184338/hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  13. melvin-bot commented on Jan 21, 2026

    @melvin-bot

    @stephanieelliott Eep! 4 days overdue now. Issues have feelings too...

  14. stephanieelliott commented on Jan 21, 2026

    @stephanieelliott
    Contributor

    Payment Summary

    Contributor: @Eskalifer1 paid $250 via Upwork
    Contributor+: @akinwale due $250 via NewDot

  15. Eskalifer1 commented on Jan 21, 2026

    @Eskalifer1
    Contributor
  16. VictoriaExpensify commented on Jan 22, 2026

    @VictoriaExpensify
    Contributor

    Sorry, I accidentally approved this payment 😅

    Image
  17. stephanieelliott commented on Jan 22, 2026

    @stephanieelliott
    Contributor

    All good, thanks @VictoriaExpensify!

  18. quinthar commented on Jan 27, 2026

    @quinthar
    Contributor

    Approved $250 to @akinwale

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.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions