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-06-01] [$250] Expense-When User A sends a manual and scan expense to User B, IOU avatar is combined #82488
Version Number: 9.3.19-1 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught during regression testing, add the test name, ID and link from BrowserStack:https://test-management.browserstack.com/projects/2219752/folder/13177029/test-cases/41237792 Email or phone of affected tester (no customers): N/A Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: MacBook Air 15.7.3 Chrome, iPhone 15 iOS 26.2.1 App Component: Money Requests
Action Performed:
Sign in to ND as User A
Create a chat with User B
Send a manual expense to User B, observe the IOU creator avatar it correctly shows User A's avatar
Send a scan expense in the same chat, observe the avatar
Expected Result:
IOU avatar should show only the expenses creator - User A
Actual Result:
When IOU in 1:1 chat contains manual and scan expense, both creator and receiver avatars are displayed above the report, as if both users created the expenses
The offending PR is #64802 by JakubKorytko (merged 2025-07-09). It introduced the areAmountsSignsTheSame logic using Math.sign(tr.amount) which doesn't account for scan expenses having amount = 0 (Math.sign(0) = 0 is distinct from Math.sign(positive) = 1).
[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.
@marufsharifi can you please accept the job below? Please reply here and tag me once you have.
If you're not sent an offer in Upwork when you're assigned to an issue, please tag me. If an Upwork job exists, please submit a proposal. https://www.upwork.com/jobs/~022061586744261678112
Activity
melvin-bot commentedon Feb 14, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @akinwale (
External)melvin-bot commentedon Feb 14, 2026
Triggered auto assignment to @sonialiap (
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 14, 2026
Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue.
109 remaining items
MelvinBot commentedon May 27, 2026
The offending PR is #64802 by
JakubKorytko(merged 2025-07-09). It introduced theareAmountsSignsTheSamelogic usingMath.sign(tr.amount)which doesn't account for scan expenses havingamount = 0(Math.sign(0) = 0is distinct fromMath.sign(positive) = 1).The fix was deployed via #87961.
aimane-chnaif commentedon May 27, 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: https://github.com/Expensify/App/pull/64802/changes#r3308190432
[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: https://github.com/Expensify/Expensify/issues/644074
Regression Test Proposal
Test:
Case 1: OP
Case 2: Zero Amount Request
Case 3: Clear Cache /
iouActionsUnavailableCase 4: Two Devices
Do we agree 👍 or 👎
Zapier Logs
Run ID: 00040eee-1716-abe0-551b-7f88283d9f24melvin-bot commentedon May 31, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)mallenexpensify commentedon Jun 1, 2026
Payment Summary
Contributor: @marufsharifi paid $250 via Upwork
Contributor+: @aimane-chnaif paid $250 via Upwork
@marufsharifi can you please accept the job below? Please reply here and tag me once you have.
If you're not sent an offer in Upwork when you're assigned to an issue, please tag me. If an Upwork job exists, please submit a proposal.
https://www.upwork.com/jobs/~022061586744261678112
^ Test case created. Thx
marufsharifi commentedon Jun 2, 2026
@mallenexpensify, I've accepted the offer. thanks.
mallenexpensify commentedon Jun 2, 2026
@marufsharifi paid, summary updated above. Thx.