Skip to content

[Due for payment 2025-07-18] [Multi-Files Drag-and-Drop] Scan - First step of scan flow reopens after changing To field and adding another receipt #65599

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.1.77-1
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 TestRail: #64941
Email or phone of affected tester (no customers): applausetester+070712kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Log in with Expensifail account.
  • Have a workspace (make sure it is the default workspace).
  1. Go to staging.expensify.com
  2. Open FAB > Create expense > Scan.
  3. Upload a receipt.
  4. On confirmation page, click on the To field (workspace chat).
  5. Select any user which is not workspace chat.
  6. Click RHP back button.
  7. Upload another receipt.

Expected Result:

RHP will open confirmation page that will have 2 receipts.

Actual Result:

The first step of scan flow reopens after changing To field and adding another receipt.

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

Bug6880848_1751926187858.20250708_060635.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @adelekennedy

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 Jul 8, 2025
  2. melvin-bot commented on Jul 8, 2025

    @melvin-bot

    Triggered auto assignment to @adelekennedy (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 Jul 8, 2025

    @melvin-bot

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

  4. melvin-bot commented on Jul 8, 2025

    @melvin-bot

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

  5. github-actions commented on Jul 8, 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. koko57 commented on Jul 8, 2025

    @koko57
    Contributor

    look slike this might be caused by #64941, I will check it

    cc @lakchote

  7. koko57 commented on Jul 8, 2025

    @koko57
    Contributor

    Checked this one too - looks like it happens when Beta is enabled

    beta enabled

    Screen.Recording.2025-07-08.at.10.13.28.mov

    beta not enabled

    Screen.Recording.2025-07-08.at.10.14.34.mov
  8. 6 remaining items

  9. added and removed
    DeployBlockerIndicates it should block deploying the API
    on Jul 8, 2025
  10. added
    ReviewingHas a PR in review
    and removed on Jul 8, 2025
  11. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jul 11, 2025
  12. changed the title [-]Scan - First step of scan flow reopens after changing To field and adding another receipt[/-] [+][Due for payment 2025-07-18] Scan - First step of scan flow reopens after changing To field and adding another receipt[/+] on Jul 11, 2025
  13. melvin-bot commented on Jul 11, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  14. melvin-bot commented on Jul 11, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.79-11 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 2025-07-18. 🎊

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

    • @koko57 does not require payment (Contractor)
  15. melvin-bot commented on Jul 11, 2025

    @melvin-bot

    @lakchote @adelekennedy @koko57 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]

  16. changed the title [-][Due for payment 2025-07-18] Scan - First step of scan flow reopens after changing To field and adding another receipt[/-] [+][Due for payment 2025-07-18] [Multi-Files Drag-and-Drop] Scan - First step of scan flow reopens after changing To field and adding another receipt[/+] on Jan 15, 2026
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.EngineeringWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions