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-04-14] Android - Report - User is auto scrolled up after returning from second added receipt. #84362
Version Number: 9.3.32.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 BrowserStack:#83994 Email or phone of affected tester (no customers):ibellicotest+2250@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Motorola MotoG60 / Android 12 (Hybrid app) App Component: Money Requests
Action Performed:
Prerequisite: Account has at least one workspace.
Open the Expensify app.
Open any workspace chat.
Create a manual expense.
Open the just created expense.
Add a receipt to the expense.
After the receipt is added, return to report.
Tap on the "Plus" button on receipt and add another receipt to report.
Open the just added receipt and tap on the back button to return to report.
Note that you are not scrolled up after returning.
Tap on the "Plus" button on receipt again and add another receipt.
Open the just added receipt and tap on the back button to return to report.
Note that when you land on report, you are autoscrolled up.
Expected Result:
After returning from a receipt added to a report, the user should remain on the bottom of report.
Actual Result:
After returning to report from the second added receipt, user is autoscrolled up.
👋 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.
Classification: Frontend bug Causing PR: #83994 - "feat: allow multiple receipts to be attached to a single expense" by @TaduJR (High confidence) Related Issues: #81435
Recommendation: REVERT
PR #83994 introduced the ability to add multiple receipts to a single expense by adding action buttons (enlarge and add receipt) directly on the receipt image in MoneyRequestReceiptView. While the feature works as intended, it has introduced an auto-scroll regression on Android that disrupts the user experience. After adding the second receipt and returning to the report, users are unexpectedly scrolled to the top instead of remaining at the bottom of the thread where they were.
This is a new feature that does not exist in production, so reverting will not remove any existing functionality from users.
Labels: This is a frontend bug caused by an App PR. The issue is reproducible only on staging (not in production since the feature is new), but I am keeping both DeployBlockerCash and DeployBlocker labels as they were added by internal team members. Per the investigation protocol, I should not remove labels added by internal employees.
📋 Detailed Analysis
Evidence
PR #83994 added two icon buttons overlaid on receipt images in MoneyRequestReceiptView:
An enlarge button that opens the receipt modal
An add receipt button that opens the attachment picker and posts files to the expense thread via addAttachmentWithComment
The PR modified:
src/components/ReportActionItem/MoneyRequestReceiptView.tsx - Added the new buttons and attachment functionality
After adding the FIRST receipt and returning to the report, the user stays at the bottom (correct behavior)
After adding the SECOND receipt and returning to the report, the user is auto-scrolled to the top (bug)
This matches the timeline: PR #83994 was merged on March 5, 2026, and is included in the staging deploy checklist (9.3.32-0). The issue was reported on March 6, 2026, and is marked as "N/A - new feature, doesn't exist in prod" - confirming this is a new feature introduced by this PR.
Root Cause
When the add receipt button is pressed, it calls addAttachmentWithComment() which creates a new report action in the thread. The InvertedFlatList (which powers the report actions view) is not maintaining the scroll position correctly after the second attachment is added. This appears to be a side effect of how the list handles scroll position when new items are added, particularly on Android.
The behavior difference between the first and second receipt additions suggests there may be an issue with how the scroll key or scroll manager handles multiple rapid additions of new content to the inverted list.
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
[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: N/A.
[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
Test:
Open an expense report with enough messages to allow scrolling
Scroll to the top
Send an attachment using the compose bar
Wait for the chat to automatically scroll to the new attachment
Open the attachment
Navigate back to the report
Verify that you are still at the bottom of the report
Issue is ready for payment but no BZ is assigned. @mallenexpensify you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks!
Activity
melvin-bot commentedon Mar 6, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #83994
melvin-bot commentedon Mar 6, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Mar 6, 2026
Triggered auto assignment to @laurenreidexpensify (
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.github-actions commentedon Mar 6, 2026
👋 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:
OSBotify commentedon Mar 6, 2026
🔍 Investigation Summary
Classification: Frontend bug
Causing PR: #83994 - "feat: allow multiple receipts to be attached to a single expense" by @TaduJR (High confidence)
Related Issues: #81435
Recommendation: REVERT
PR #83994 introduced the ability to add multiple receipts to a single expense by adding action buttons (enlarge and add receipt) directly on the receipt image in MoneyRequestReceiptView. While the feature works as intended, it has introduced an auto-scroll regression on Android that disrupts the user experience. After adding the second receipt and returning to the report, users are unexpectedly scrolled to the top instead of remaining at the bottom of the thread where they were.
This is a new feature that does not exist in production, so reverting will not remove any existing functionality from users.
Labels: This is a frontend bug caused by an App PR. The issue is reproducible only on staging (not in production since the feature is new), but I am keeping both
DeployBlockerCashandDeployBlockerlabels as they were added by internal team members. Per the investigation protocol, I should not remove labels added by internal employees.📋 Detailed Analysis
Evidence
PR #83994 added two icon buttons overlaid on receipt images in
MoneyRequestReceiptView:addAttachmentWithCommentThe PR modified:
src/components/ReportActionItem/MoneyRequestReceiptView.tsx- Added the new buttons and attachment functionalitysrc/CONST/index.ts- Added button constantssrc/styles/index.ts- Added button positioning stylesVerification
The bug report states that:
This matches the timeline: PR #83994 was merged on March 5, 2026, and is included in the staging deploy checklist (9.3.32-0). The issue was reported on March 6, 2026, and is marked as "N/A - new feature, doesn't exist in prod" - confirming this is a new feature introduced by this PR.
Root Cause
When the add receipt button is pressed, it calls
addAttachmentWithComment()which creates a new report action in the thread. The InvertedFlatList (which powers the report actions view) is not maintaining the scroll position correctly after the second attachment is added. This appears to be a side effect of how the list handles scroll position when new items are added, particularly on Android.The behavior difference between the first and second receipt additions suggests there may be an issue with how the scroll key or scroll manager handles multiple rapid additions of new content to the inverted list.
TaduJR commentedon Mar 6, 2026
Investigating...
25 remaining items
ahmedGaber93 commentedon Apr 13, 2026
BugZero Checklist:
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR: https://github.com/Expensify/App/pull/18402/changes#r3075176053
Link to the comment on the Issue: [HOLD for payment 2023-06-15] [HOLD for payment 2023-05-31] [$4000] App does not hold scroll position and scrolls to top in LHN on tapping back button from chat page #14125 (comment)
[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: N/A.
[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
Test:
Do we agree 👍 or 👎
melvin-bot commentedon Apr 14, 2026
Issue is ready for payment but no BZ is assigned. @mallenexpensify you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks!
melvin-bot commentedon Apr 14, 2026
Payment Summary
Upwork Job
BugZero Checklist (@mallenexpensify)
laurenreidexpensify commentedon Apr 15, 2026
@TaduJR pls apply to upwork job - upwork.com/jobs/~022044411967766116329
TaduJR commentedon Apr 15, 2026
Applied @laurenreidexpensify
Thanks!
laurenreidexpensify commentedon Apr 16, 2026
Payment Summary
flaviadefaria commentedon Apr 29, 2026
$250 approved for @ahmedGaber93