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
Version Number: 9.1.72-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from TestRail:https://expensify.testrail.io/index.php?/tests/view/6375775 Email or phone of affected tester (no customers):sdhiuhsisudhsdisi@gmail.com Issue reported by: Applause Internal Team Device used: Mac 15.5 / Chrome App Component: Money Requests
👋 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.
perf: transactions and violations by reports derived value #63655: This PR overhauls how transactions and violations are aggregated via a new derived value configuration across many report components. The deletion of an expense triggers updates in these lists, and if the new aggregation logic does not gracefully handle the removal of an expense, it could lead to state or data inconsistencies that crash the app.
[Contributor] 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:
[Contributor] 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.
Regression Test Proposal Template
[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
Precondition:
Test:
1. Open 1:1 DM with a new user.
2. Submit two expenses to the user.
3. Open expense report.
4. Select all expenses via checkbox.
5. Click + > Create expense > Manual.
6. Submit another expense to the user.
7. Click on the expense from Step 7.
8. Send a reply to the expense thread.
9. Click on the report header.
10. Click Delete expense.
11. Delete the expense.
12. Verify the app does not crash and the expense is deleted
Activity
melvin-bot commentedon Jun 28, 2025
Triggered auto assignment to @maddylewis (
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 Jun 28, 2025
Triggered auto assignment to @puneetlath (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jun 28, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jun 28, 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:
BlameGPT commentedon Jun 30, 2025
Possible culprit PRs for this issue
rushatgabhane commentedon Jun 30, 2025
@hoangzinh @TMisiukiewicz do you think #63655 caused this?
90 remaining items
melvin-bot commentedon Sep 8, 2025
@puneetlath, @Ollyws, @jliexpensify, @Krishna2323 Whoops! This issue is 2 days overdue. Let's get this updated quick!
jliexpensify commentedon Sep 9, 2025
Deployed to prod
[-][$500] Expense - App crashes after deleting expense[/-][+][PAY 12TH SEP][$500] Expense - App crashes after deleting expense[/+]jliexpensify commentedon Sep 9, 2025
Automation is broken, @Ollyws can we get the checklist please?
Ollyws commentedon Sep 12, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] 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: https://github.com/Expensify/App/pull/52740/files#r2344847970
[Contributor] 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:
[Contributor] 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
Precondition:
Test:
Do we agree 👍 or 👎
jliexpensify commentedon Sep 14, 2025
Payment Summary
Krishna2323 commentedon Sep 14, 2025
Requested in ND!
Ollyws commentedon Sep 15, 2025
Requested in ND.
quinthar commentedon Sep 17, 2025
Approved $250 for @Krishna2323
flaviadefaria commentedon Sep 19, 2025
Approved $500 for for @Ollyws