You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-08-20] Merge - Unable to merge expenses while in offline mode. #68169
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.
Open the staging.new.expensify.com website.
Open any workspace chat.
Create a manual expense.
Navigate to another workspace chat.
Submit a different manual expense.
Open the just created expense.
Tap on "More" and select "Merge"
Note that the first created expense is displayed as available to merge.
Return to report.
Turn off internet connection.
Tap on "More" and select "Merge"
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.
👋 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:
Identify the pull request that introduced this issue and revert it.
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
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:
@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]
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.
Activity
melvin-bot commentedon Aug 8, 2025
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.melvin-bot commentedon Aug 8, 2025
Triggered auto assignment to @francoisl (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Aug 8, 2025
👋 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:
melvin-bot commentedon Aug 8, 2025
💬 A slack conversation has been started in #expensify-open-source
13 remaining items
[-]Merge - Unable to merge expenses while in offline mode.[/-][+][Due for payment 2025-08-20] Merge - Unable to merge expenses while in offline mode.[/+]melvin-bot commentedon Aug 13, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Aug 13, 2025
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. 🎊
melvin-bot commentedon Aug 13, 2025
@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]
melvin-bot commentedon Aug 20, 2025
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.
mallenexpensify commentedon Aug 21, 2025
@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
mallenexpensify commentedon Aug 25, 2025
@dominictb 👀 above plz
dominictb commentedon Aug 25, 2025
Yeah I'll be paid via #65574. Please close this one.