Repository navigation
[Due for payment 2025-04-18] [Due for payment 2025-03-05] [Due for payment 2025-03-05] Reports - Expense preview shows "owes" instead of "paid" when the expense is paid #57347
Description
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.5-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to check
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): applausetester+sj9032@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.0 / Chrome
App Component: Search
Action Performed:
- Go to staging.new.expensify.com
- Create a new workspace.
- Go to workspace chat.
- Submit an expense.
- Click Submit on the expense preview.
- Click Approve.
- Click Pay elsewhere.
- Open another chat.
- Send a message.
- Go to account settings > Troubleshoot > Clear cache and restart.
- Click Reset and refresh.
- After the app loads, go to Reports > Chats.
- Note that the expense preview shows "owes" instead of "paid".
Expected Result:
The expense preview will show "paid" as the expense is paid.
Actual Result:
The expense preview shows "owes" instead of "paid".
Workaround:
Unknown
Platforms:
- Android: Standalone
- Android: HybridApp
- Android: mWeb Chrome
- iOS: Standalone
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
Activity
melvin-bot commentedon Feb 24, 2025
Triggered auto assignment to @VictoriaExpensify (
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 Feb 24, 2025
Triggered auto assignment to @aldo-expensify (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Feb 24, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Feb 24, 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:
vincdargento commentedon Feb 24, 2025
@VictoriaExpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.
melvin-bot commentedon Feb 25, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
melvin-bot commentedon Feb 25, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
19 remaining items
melvin-bot commentedon Feb 26, 2025
@aldo-expensify @VictoriaExpensify @aldo-expensify 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]
Fix Expensify#57347, Prettier
melvin-bot commentedon Apr 10, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
melvin-bot commentedon Apr 10, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
[-][Due for payment 2025-03-05] [Due for payment 2025-03-05] Reports - Expense preview shows "owes" instead of "paid" when the expense is paid[/-][+][Due for payment 2025-04-18] [Due for payment 2025-03-05] [Due for payment 2025-03-05] Reports - Expense preview shows "owes" instead of "paid" when the expense is paid[/+]melvin-bot commentedon Apr 11, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Apr 11, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.26-10 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-04-18. 🎊
melvin-bot commentedon Apr 11, 2025
@aldo-expensify @VictoriaExpensify @aldo-expensify 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]
IuliiaHerets commentedon Jun 3, 2025
Issue not reproduced anymore
20250603_170032.mp4