Skip to content

[Due for payment 2025-08-20] Merge - Unable to merge expenses while in offline mode. #68169

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.91-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 TestRail: #65596
Email or phone of affected tester (no customers): ibellicotest+1544@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app) - Windows 10 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least two workspaces.

  1. Open the staging.new.expensify.com website.
  2. Open any workspace chat.
  3. Create a manual expense.
  4. Navigate to another workspace chat.
  5. Submit a different manual expense.
  6. Open the just created expense.
  7. Tap on "More" and select "Merge"
  8. Note that the first created expense is displayed as available to merge.
  9. Return to report.
  10. Turn off internet connection.
  11. Tap on "More" and select "Merge"
  12. Note that a "No elegible expenses found" message is displayed.

Expected Result:

User should be able to find elegible expenses to merge despite being in offline mode.

Actual Result:

"No elegible expenses found" message is displayed when trying to select expenses to merge while in offline mode.

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

Bug6910996_1754620596031.Merge.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @mallenexpensify

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

    @melvin-bot

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

    @melvin-bot

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

  4. github-actions commented on Aug 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.
  5. melvin-bot commented on Aug 8, 2025

    @melvin-bot

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

  6. 13 remaining items

  7. changed the title [-]Merge - Unable to merge expenses while in offline mode.[/-] [+][Due for payment 2025-08-20] Merge - Unable to merge expenses while in offline mode.[/+] on Aug 13, 2025
  8. melvin-bot commented on Aug 13, 2025

    @melvin-bot

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

  9. melvin-bot commented on Aug 13, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.93-7 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-08-20. 🎊

  10. melvin-bot commented on Aug 13, 2025

    @melvin-bot

    @youssef-lr @mallenexpensify 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. melvin-bot commented on Aug 20, 2025

    @melvin-bot

    Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.

  12. mallenexpensify commented on Aug 21, 2025

    @mallenexpensify
    Contributor

    @dominictb Looks like the PR linked to two issues, I'm going to assume you'll be paid below, comment if not. Otherwise I'll close in a day or few

  13. mallenexpensify commented on Aug 25, 2025

    @mallenexpensify
    Contributor

    @dominictb 👀 above plz

  14. dominictb commented on Aug 25, 2025

    @dominictb
    Contributor

    Yeah I'll be paid via #65574. Please close this one.

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.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions