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 2026-01-20] [$250] Android - Report - Three expenses preview briefly displayed after splitting an expense. #76754
Once redirected to report, note that three expenses preview are briefly visible, before the two splits remain shown on report.
Expected Result:
After splitting an expense, only the two splits should be visible on report.
Actual Result:
After splitting an expense, original expense is still briefly visible among the two splits. The three previews can be seen for a moment, before the two splits remain displayed.
👋 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 [-][$250] Android - Report - Three expenses preview briefly displayed after splitting an expense.[/-][+][Due for payment 2026-01-20] [$250] Android - Report - Three expenses preview briefly displayed after splitting an expense.[/+]on Jan 13, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.99-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@bernhardoj@lydiabarclay 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]
[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: The offending code has been there for some months since the initial implementation, so it could be some performance issue that reveals this issue.
[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.
This was caught on an existing test case, so no need to create a new test case.
Activity
melvin-bot commentedon Dec 4, 2025
Triggered auto assignment to @lydiabarclay (
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 Dec 4, 2025
Triggered auto assignment to @MariaHCD (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Dec 4, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Dec 4, 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:
48 remaining items
[-][$250] Android - Report - Three expenses preview briefly displayed after splitting an expense.[/-][+][Due for payment 2026-01-20] [$250] Android - Report - Three expenses preview briefly displayed after splitting an expense.[/+]melvin-bot commentedon Jan 13, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jan 13, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.99-8 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 2026-01-20. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jan 13, 2026
@bernhardoj @lydiabarclay 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]
bernhardoj commentedon Jan 13, 2026
BugZero Checklist:
[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: The offending code has been there for some months since the initial implementation, so it could be some performance issue that reveals this issue.
[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.
This was caught on an existing test case, so no need to create a new test case.
lydiabarclay commentedon Jan 20, 2026
Payment Summary
Contributor: @rohit9625 paid $250 via Upwork
Contributor+: @bernhardoj due $250 via NewDot
✅ No regression test needed
bernhardoj commentedon Jan 21, 2026
Requested in ND.
garrettmknight commentedon Jan 21, 2026
$250 approved for @bernhardoj